I would think that form action should  work unless there might be an issue with a searchable user field or the user not available in the list.  Is the user selectable in the field without the form action?

There is a couple of ways without an appscript. You could set the default in Web Admin for the transition:

If it is a searchable field, you could maybe make non-searchable (if possible) or you could select to create a form action "Execute Javascript" and do the following, as it forces the search on the field:

SetFieldValue("Data Entry Specialist", \{'id':{_UserId}, 'name':'{_UserName}')

MichaelCFiala  Thanks for the reply! Can I know where can I find that screenshot in the admin portal please? and where can I find such that javascript examples? I didn't find it the sbms_js_library.pdf documentation

You'll set defaults at the project level, which allows you to have defaults for different projects within SBM.

To access the screen, go to "Application Administrator > Projects > [Your Project] > States/Transitions > [Your Transition]  Details > Fields > [Data Entry Specialist] Details > Set Allow Override & Set to Value to Default Value > Manage Group Users Default"

Here is information on the SetFieldValue. Look at the last example: https://docs.microfocus.com/doc/Solutions_Business_Manager/12.1/ttst_set_field_value

For setting user defaults, you can also set them at the workflow in the Application Administrator.

"Application Administrator > Workflows > [Your Workflow] > States/Transitions > [Your Transition]  Details > Fields > [Data Entry Specialist] Details > Set Allow Override & Set to Value to Default Value > Manage Group Users Default"

MichaelCFiala  Thank you for sharing that info! I have the sbms_js_library.pdf documentation and know the functions of SBM javascript such as SetFieldValue and others, but my question was its not mentioned in that documentation what are the built-in variables that we can utilize such as UserName etc.

For those built in variables, I don't know if they are noted in the documentation but I've come across them while working on form actions. To access them, when you are adding an action, type { and you will see all of the available fields on the form, but if you scroll down of the options you'll find the _UserName, _UserId, _TableId, etc.

Thanks a lot, appreciated!

Your experience with AppScript in this context is one of the main reasons I encourage SBM developers to avoid scripting .... I have seen too many developers discover AppScript then use it as the "universal solution" to any problem because they haven't learned all the features and capabilities of SBM.  There are almost always alternative approaches that can be used.  A script will have to be maintained, and probably by a developer who doesn't know AppScript.

PM Thompson  I agree