Is this all expected behavior? If you manually cancel a sub-process node, the pr

Jason Ruvinsky

Certified Senior Developer

over 11 years ago

Is this all expected behavior? If you manually cancel a sub-process node, the process instance triggered by that node does not get cancelled. However, if there is an exception flow on the sub-process node, the process instance triggered by the node DOES get cancelled.

A further wrinkle if you introduce MNI on the node: if there is an exception flow that triggers, only one instance of the node and sub-process is cancelled, and the others are unaffected....

Discussion posts and replies are publicly visible

0 Patty Isecke
Appian Employee
over 11 years ago

Does this behavior differ for the type of user (Basic vs. Admin)? Are you activity chaining? How have you configured your sub-process? Is it asynchronous or synchronous?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jason Ruvinsky
Certified Senior Developer
over 11 years ago

We are running sub-process nodes as the designer (Administrator). In these cases, there is no activity chaining, and the sub-processes are synchronous. (For the MNI case, the node is configured to move on when all instances are completed). Yes the sub-process is configured.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel