Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
7 replies
Subscribers
6 subscribers
Views
2344 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hi Forum I have a quicktask with it's own process flow as well as
lincolnf454
over 11 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...
OriginalPostID-90198
OriginalPostID-90198
Discussion posts and replies are publicly visible
Parents
0
Mike Cichy
Appian Employee
over 11 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
Reply
0
Mike Cichy
Appian Employee
over 11 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
Children
No Data