You are viewing limited content. For full access, please sign in.

Question

Question

Process Diagram - Multiple Approvers

asked on November 24

I have an inclusive gateway for multiple approvers.  See diagram below:

 

This is based on the user selecting the necessary approvers:

The way I have the diagram structured, everyone is assigned a task at the same time, and the process will wait until all approvals have been completed.  What I need to do is have the approvals done one at a time, so check if the box is checked and if it is assign the task.  When the task is completed, check the next box and if it is checked assign the task, and so on.  Any help would be appreciated.  Thanks!

0 0

Answer

APPROVED ANSWER
replied on November 24 Show version history

You shouldn't have multiple in/out on the same gateway. The recommended approach is to have each one either merge, or split, but not both. I feel like that used to only cause a warning, but it does show as an error now.

Because you're going with a linear process, you can use all exclusive gateways (i.e., it's either going left or right, never both).

Something like this:

I tend to make my "No" paths the default in situations like this where the "Yes" path is tied to one specific value/selection.

0 0

Replies

replied on November 24

You want to diagram so that it is more linear with inclusive gateways.  This would check after each submission to decide if it would assign the task to the next checkbox option:

0 0
replied on November 24

Hello Craig, thanks for your reply.  When I try your method, I'm getting messages that I cannot have multiple incoming and outgoing sequence flows on gateways.

0 0
replied on November 24

Make sure you're using an inclusive gateway.  You will see that error if you're attempting to use an exclusive gateway.

0 0
replied on November 24

I checked and I am using inclusive gateways.

0 0
APPROVED ANSWER
replied on November 24 Show version history

You shouldn't have multiple in/out on the same gateway. The recommended approach is to have each one either merge, or split, but not both. I feel like that used to only cause a warning, but it does show as an error now.

Because you're going with a linear process, you can use all exclusive gateways (i.e., it's either going left or right, never both).

Something like this:

I tend to make my "No" paths the default in situations like this where the "Yes" path is tied to one specific value/selection.

0 0
replied on November 25

Thanks Jason and Craig!  The linear approach works perfectly.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.