Correct execution of User Tasks in a workflow is often dependent on variable settings prior to them receiving the token. Because of this, using the Nav to go back while the workflow is in progress can usually be done without issue. But going back after the workflow is complete can be problematic. Because of this, disable the Nav after the workflow is complete.
An example of problems if the user uses the Nav to "restart" the workflow is the Protocol, Application and Cover Sheet workflow. Restarting with the Restart button (without clearing data) will not resend the automatic emails since the Load Data Script Task is executed and the Protocol is found to be already uploaded. If the Nav is used to go back to any of the User Tasks, the initial setting that the Protocol is not uploaded is in the Task Data and the automatic emails will be resent.
We should discuss this ticket as a team first since there may be other approaches to fixing the root cause in play with the current discussions we are having on how we handle our data.
calexh-sar
commented
2 years ago
Correct execution of User Tasks in a workflow is often dependent on variable settings prior to them receiving the token. Because of this, using the Nav to go back while the workflow is in progress can usually be done without issue. But going back after the workflow is complete can be problematic. Because of this, disable the Nav after the workflow is complete.
An example of problems if the user uses the Nav to "restart" the workflow is the Protocol, Application and Cover Sheet workflow. Restarting with the Restart button (without clearing data) will not resend the automatic emails since the Load Data Script Task is executed and the Protocol is found to be already uploaded. If the Nav is used to go back to any of the User Tasks, the initial setting that the Protocol is not uploaded is in the Task Data and the automatic emails will be resent.
We should discuss this ticket as a team first since there may be other approaches to fixing the root cause in play with the current discussions we are having on how we handle our data.