Designer 10.5 | webMethods BPM Process Development Help | Gateway Steps | About Gateway Types
 
About Gateway Types
Designer represents a gateway as a yellow diamond shape. The following table lists the four different icons which represent the four gateway types:
Gateway
Behavior
Exclusive gateway icon Exclusive (XOR, or Unsynchronized OR)
Diverging behavior:
*Only one of the available output transition paths can be taken.
*The default transition path (optional) is taken if none of the conditions on the other transition paths are true.
*If no transition path is true and a default path is not available, a run-time exception occurs.
Converging behavior:
*Each input transition path is routed to the output transition path without synchronization (an Unsynchronized OR join).
Invclusive gateway icon Inclusive (OR, or Synchronized OR)
Diverging behavior:
*All of the available output transition paths that evaluate to true are taken. That is, parallel output transition paths are possible.
*The default transition path (optional) is taken if none of the conditions on the other transition paths are true.
*If no transition path is true and a default path is not available, a run-time exception occurs.
Converging behavior:
*All input transition paths are merged in a synchronized OR join.
Complex gateway icon Complex (webMethods)
Diverging behavior is based on output transition conditions. Converging behavior supports join types: AND, OR, and unsynchronized OR. A join timeout is supported.
Note:
Current webMethods gateways migrate to complex gateways visually only (no generation or model changes).
Parallel gateway icon Parallel (AND)
Diverging behavior:
*All of the available output transition paths that evaluate to true are taken. That is, parallel output transition paths are possible.
*The default transition path (optional) is taken if none of the conditions on the other transition paths are true.
*If no transition path is true and a default path is not available, a run-time exception occurs.
Converging behavior:
*All input transition paths are merged in an AND join (waits for all inbound paths). A join timeout is supported.
Always be sure you are adding the correct gateway type to your process. Incorrect usage or configuration can create unexpected run-time results.
For example, you can configure an exclusive gateway with two separate output transition with two separate but identical conditions, expecting that each path will be taken when the conditions are matched. However, only one of the paths will be randomly selected, because single-path operation is the defined behavior of an exclusive gateway. For this scenario, the best choice is an inclusive gateway.
Related Topics