Best Practice around Terminating Quick Task : Use-case : Employe

Best Practice around Terminating Quick Task :

Use-case :
Employee creates a Request and the flow keeps waiting till a trigger date. During this time, employee can edit and update the details of the request. This we have implemented using Quick Task.

Problem Faced :
The form has validations. During Edit (which is the Quick Task), employee submits the form with updated values, validation happens in the Script tasks, and if validation fails the control comes back to the same Edit screen. Problem is, now 2 instances of the same Edit quick task is shown in Related Tasks. If validation fails 1 more time, then 1 more Quick Task instance is created. It goes on like this.

Solution Adapted:
The Edit screen (Quick Task) is set with an Exception flow which will go to End if a boolean flag is set. We set this flag when we go out of the Edit screen (when user submits it) and once validation fails, this flag is reset. So, this way the old instance of the Quic...

OriginalPostID-103878

OriginalPostID-103878

  Discussion posts and replies are publicly visible

Parents Reply Children
No Data