1) A dropdown field with Accept, Reject, or Not Applicable is tied to an "initial" field to the right of it.
2) When the dropdown field is FIRST POPULATED or CHANGED, the "initial" field automatically populates with the Current User's name
3) This is hardcoded and the user can not change or remove this.
4) This means that, even after submitted / saved, if another user comes in and changes one of the dropdowns, it will then hardcode to THEIR username.
Thinking about it, I feel like there might be a very round-about-way to do this with rules inside of mobile. Like... if a user selects a dropdown (if not nullorempty and if username blank) then populate their name in the initial (then user CurrentUser to populate Initial).
The problem I have is the next bit -- if a user saves, submits, etc, and another user opens it and changes it .... best I can figure right now is that I need 2 fields. One for "written to field" after submission / save (which a workflow would pickup, clear out, and write)... and one to say "hey i'm empty because in this particular instance of this form being opened, no one has changed this attached field."
I think it's an interesting problem likely with many ways to solve and thought it might be fun to think about together. Let me know what you think.
Regarding populating the current user upon creation and not having to change it everytime the form opens with another.
We can do a read only field with the "default value" being the current logged in person. This will get populated upon creation and if it is read only, then the users won't able to change it. It will make the default value dynamic (only when first created) . I hope I understood this correctly.