Question

Stop Parallel Approvers if one Approver Rejects

Forms

Updated July 19, 2021

asked on June 14, 2017 • Show version history

Hello,

In forms I am trying to send a form to multiple approvers at one time using a parallel gateway. If one rejects I want to remove the task from all other approvers. I have added a throw and catch event that is set to stop the current activity on all other approvers but the process wants me to attach an end event to the catch. If I attach an end event it stops the whole process- If I attach the catch to the next step in the process (a exclusive decision) it creates a task for each catch event, so if one approvers rejects and two catch's are thrown the next step shows three tasks (the same task)- one for each approver. Any help would be appreciated!

Thanks!

Terri

PROCESS.png (76.28 KB)

| Download

0 0

Answer

SELECTED ANSWER

replied on June 14, 2017 • Show version history

Hi Jason,

Thank you for responding! I connected them with their own end event. I actually want them to continue with the process but skip the requirement where all approvers approve in the parallel activity. I do not want them to terminate the process at all.

1 0

Replies

replied on June 14, 2017 • Show version history

Are you sure you were connecting them to their own End Event and not a Terminate End Event or the same one at the end of the process? It would help to see the process history to determine exactly what happens up to the point where the process ends.

I have a similar parallel approval process and mine is working as expected. One difference with mine is that I merge the output of the parallel tasks to utilize a shared signal throw event that is triggered by whichever one is completed first.

0 0

SELECTED ANSWER

replied on June 14, 2017 • Show version history

Hi Jason,

1 0

replied on June 14, 2017 • Show version history

Right, that is what happens in my process. If any 1 of the multiple parallel approvers approve or reject the form, it proceeds to the next step. The only tasks that are cancelled are the other parallel tasks that are no longer required.

For example,

User submits a form
Parallel asks are assigned to User 1, User 2 and User 3
User 3 Approves/Rejects the form
Signal throw is triggered - Tasks for User 1 and User 2 are cancelled
Process continues to the next step(s)

If you attach a normal End Event to the signal catches, it should only stop that specific branch, not the entire process. The idea is that all branches have to lead to some kind of end event even if the user task is cancelled.

It sounds like you should have something more like this:

Out of curiosity, why do you have two branches coming out of those Exclusive Gateways? It seems like that would give it the option of bypassing the signal throw to allow all three processes to go through.

1 0

replied on June 14, 2017

update- I must have changed something else- I added the end event back to each catch event and it proceeds correctly. Thank you for helping Jason!

0 0

replied on July 19, 2021

I have 3 approvers connected to a parallel gateway.

If all the 3 of them approves, the process should continue to the Final Reviewer.

If one of them rejects, the process should stop and not continue to the Final reviewer.

It works with the Signal Throw and Catch event. But the instance status is not shown as completed, but shows as 'In Progress'.

For e.g. when Approver 1 approves and Approver 2 rejects, in the instance history it shows that Approver 3 user task as Interrupted.

Though it shows as 'In Progress' there are no further tasks to be completed.

Any help would be appreciated.

0 0

You are not allowed to follow up in this post.

Question

Question

Stop Parallel Approvers if one Approver Rejects

Answer

Replies

Sign in to reply to this post.