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

senthilar over 11 years ago

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...

Discussion posts and replies are publicly visible

0 senthilar over 11 years ago

...k Task is killed and only the new instance remains. Our requirement is satisfied this way and it fulfills our use case.

But is our approach in tune with the Best Practice around this scenario? If not, how should we handle this problem?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Rick Bivin
Appian Employee
over 11 years ago

On the "Other" tab of the Quick Task properties, find the "When this node is re-executed:" and select "Delete previous instances that are still active." This will ensure no more than 1 quick task is created.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 senthilar over 11 years ago

Thank you much Richard! This seems to be the right approach!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel