Exclusive Gateway

•When two or more transitions exit this shape at least one should be “Else”. The other outgoing sequence flows must have business conditions for Bizagi to evaluate. Only one can be met.

•This figure is also used to synchronize paths. The first token to reach the shape will continue the flow.

Basic Properties

•Display Name: This is the display name of the Gateway that is shown in the Work Portal.

•Name: This is the name of the Gateway in database.

•Description: Displays additional information for the Gateway.

Event Based Gateway

•A transition that exits this shape cannot enter a Sub-Process, Multiple Sub-Process or Exclusive Gateway.

•Valid shapes following this shape are Tasks, and Events.

Note: The Event Based Gateway should not have shapes that execute automatically after it. We strongly suggest using the following shapes:

oManual Tasks

oConditional Tasks

oNone Events

oTimer Events

oBot Tasks

oReceive Tasks

Basic Properties

•Display Name: This is the display name of the Gateway that is shown in the Work Portal.

•Name: This is the name of the Gateway in database.

•Description: Displays additional information for the Gateway.

Parallel Gateway

•The paths out of the figure do not require business rules since all paths must be followed.

•When the gate is used as a convergent element (synchronization) it continues along only one path; conversely, when it is used as a divergent element there are many paths to continue.

•It is strongly recommended using a Parallel Gateway used as a convergent element after one or more Parallel Gateways used as a divergent elements, to be able to synchronize.

Basic Properties

•Display Name: This is the display name of the Gateway that is shown in the Work Portal.

•Name: This is the name of the Gateway in database.

•Description: Displays additional information for the Gateway.

Complex Gateway

•As a divergence element, when a Process reaches this element, the allocated user will be presented with a user interface that shows the names of the Activities following this shape as options.

Note: This is the only gateway that is executed by a user, therefore, you need to define work allocation components.

•The user interface can be configured as an Activity form.

•As a convergence element the business condition will be evaluated at this point in the Process every time a transition arrives at this shape.

Basic Properties

•Display Name: This is the display name of the Gateway that is shown in the Work Portal.

•Name: This is the name of the Gateway in database.

•Description: Displays additional information for the Gateway.

Inclusive Gateway

•When you use an Inclusive Gateway (divergence element), make sure there is at least one valid path. We recommend to add a transition with "Else" condition in case none of the conditions is fulfilled.

•As a divergence element at least one path should be activated to be able to continue with the Process flow.

•As a convergence element, more than one sequence flow should reach it, and just one sequence flow should exit from it.

•Inclusive Gateways must be defined in pairs if they are going to be synchronized. One Inclusive Gateway (divergent element) must be defined to activate the paths and another Inclusive Gateway (convergent element) to synchronize them.

Basic Properties

•Display Name: This is the display name of the Gateway that is shown in the Work Portal.

•Name: This is the name of the Gateway in database.

•Description: Displays additional information for the Gateway.

Extended Properties

•Expressions or actions: On Enter and On Exit expressions can be associated to Gateways.