A customer created a field on a user task for that happens immediately after submission.
They put the default value to be the token
However the field is left blank when the task is opened. And in the monitor screen the variable does not exist.
A customer created a field on a user task for that happens immediately after submission.
They put the default value to be the token
However the field is left blank when the task is opened. And in the monitor screen the variable does not exist.
Is that screenshot where you set the default value on the user task form? Is that variable used on the starting form first and submitted as blank? If the field was loaded on to the initial form and submitted as a blank, that submitted blank will take precedence over a default value. You need to remove the field from the starting form if you want a default to load on a user task.
I have verified that it is not on their starting form by checking the variable name of the field and making sure the variable appears in bold in the list of variables when editing the starting form. This is the best way to ensure the variable is not used in any way before the user tasks.
Is there a lookup or something else that might override the default value in the user task? If you send over the process or open a support case, we can take a closer look. At this point, I'm just guessing.
We found that it works if the Form is read only instead of the task being read-only.
To clarify: There are 2 ways to make a user task form read only. On the form itself, or from the task.
You can do it on the form, but if you set read only on the task, the default value never gets set.
Hope this previous post helps:
I'm new to Laserfiche but your question helped me learn something new.
I did already ensure that they are using the variable on a user task after the starting form. Still it is empty, the variable just doesn't exist.
Go to the Monitor page for the instance and see what shows up in the Initiator column for the instance. If there is data there, the variable exists. Your issue is with how it's being configured to load into the form.
Is that the started by column? It is populated, but that is not exactly a username like the initiator variable. The initiator variable is hidden from view or does not exist at all on any instances of any processes when using the Monitor tab.