cancel
Showing results for 
Search instead for 
Did you mean: 

Multi-Instance task not triggering

srobinson
Champ in-the-making
Champ in-the-making
I have a multi-instance review task that is not sequential.  This review task is within a sub-process.  I use an error event to interrupt the review when a reviewer sends the content back for changes.  When there is a single user performing the multi-instance, the sub-process stops all review tasks as expected within the sub-process, however, when there are more than one reviewer in the multi-instance, all reviewers must complete before the exclusive gateway triggers the error event.

My question is as follows: Is there a way to get the gateway to trigger on the first user that sends the review back for changes?  I know that you can have a certain percent complete to trigger it, but I only need to trigger a certain percentage when it is sent back for changes.  It needs to remain at 100% for all users other wise.

Any insight on this is greatly appreciated.

- Shannon
1 REPLY 1

srobinson
Champ in-the-making
Champ in-the-making
I answered my own question.  I put in a completion condition that evaluated the decision made and now it is triggering as expected.  I entered the following in the completion condition:

${wf_reviewOutcome == 'Requires Changes' || wf_reviewOutcome == 'Reject'}

- Shannon
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.