The backend Processes that occur from the moment a form is opened until the time the saving is completed
User-configured forms are normally full of various conditional actions and workflow rules, some of which depend on data that comes from other forms. It’s important to have an understanding of the flow that the system follows when a user opens a form, fills it out, and taps the Save button. That process is detailed here.
Form opened by a user
Populate and computes conditional actions run. Values display in fields if applicable, but data has not yet been committed/saved.
As data is entered, when a field loses focus, conditions are evaluated for Hiding, Disabling, Populating, and Popup message conditional actions that depend on that field.
The form is saved by the user
Computations re-run
All Data is saved
Edit checks run
Cohort is updated based on the condition
Randomization is filled (if applicable)
ePRO diary is built if the form is the trigger for a diary configuration
Email Notifications are sent
Tasks are created
Form programming that runs after data is saved
Be cautious of populating or computing fields based on data that will not exist until the process is complete. For example, don’t populate a field based on randomization if the populate is being done on the same form where randomization occurs. Based on the order of the list above, values have already been populated by the time randomization occurs.
Another common example is populating a value based on data that is coming from the same form. In that case a user would need to save the form twice.