Hi Forum I have a quicktask with it's own process flow as well as

lincolnf454 over 10 years ago

Hi Forum

I have a quicktask with it's own process flow as well as a primary process flow in a subprocess. I'd like to disable this quicktask at the end of the primary process flow so that the primary process flow can exit the sub process and join the parent process model once again. Currently whilst debugging my process, the process stalls at the sub process since it reads the quicktask as an unattended activity node - the process cannot continue.

The documentation on disabling a quicktask reads -
"Once a quick task has been enabled, it can be disabled in one of the following ways:
The Quick Task may have an exception event configured. When the conditions for this event become true, the exception is triggered, and the Quick Task is disabled. (Exception conditions are only evaluated when an activity is first activated.) "

I understand how I would create an exception flow from the quicktask in the 'Exceptions' tab of the quicktask's properties w...

Discussion posts and replies are publicly visible

0 lincolnf454 over 10 years ago

...indow but it's not very clear on how I would disable the node itself

Any help would be greatly appreciated!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 shelzle over 10 years ago

You create a PV type boolean "qt_enabled". An exception checks whether this PV is "true". The exception flow goes to an end event. As soon as you set the PV to "false" this QT is disabled.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lincolnf454 over 10 years ago

Hi Shelzle, thanks for the timely response

I hope I'm not making myself unclear, but I don't think that connecting an exception flow to an end event will disable the quicktask node itself. In your case, the user would fire the quicktask, it would read the PV being false and then end that specific task, but the quicktask will still be active. How do I deactivate a quicktask essentially?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 shelzle over 10 years ago

Please try it out. This is exactly the way I do it in several models. The user is no doing anything.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Cichy
Appian Employee
over 10 years ago

Stefan is correct, an exception trigger deactivates any task, including quick tasks. A different pattern may be preferred: using a terminate trigger on the End Event. Triggering terminate will "kill" any activity in the process instance and complete it. Every process model should have at least one terminate event.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 venkats533 over 10 years ago

Once any process reaches terminate node (End Event with a circle in the middle), all QTs in that process will be disabled.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lincolnf454 over 10 years ago

Thank you for your responses. Maybe this aspect should be highlighted in the documentation, because as it stands, the documentation is very vague with regards to terminating QT's
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel