Gateway Control Types
Go Up to Gateways (BPM)
You can set control types for gateways. A control type changes the logic and also the symbol it represents. The table below lists all the available control types for a gateway.
Control Type | Icon | Explanation |
---|---|---|
These are the most common gateways used. A data token traverses the Process Flow arriving at the gateway. It can only go out on one flow. This control type is represented by either a diamond with an “x” in the middle or blank diamond shape. | ||
Decision: This represents a branching point where the alternatives are based on an event occurring at that point. Merge: The exclusive merge models data-based or event-based merges. Only one of the many inputs is chosen as the output. | ||
Decision: This expression represents a branching point in a Process or Choreography where the alternatives are based on an event occurring at that point. An Event-Based Gateway is considered Exclusive in a Process when the senders following the gateway are the same and the choice of which message to send depends on the same participant. Merge: The exclusive merge models data-based or event-based merges. Only one of the many inputs is chosen as the output. | ||
Decision: One or more of the outgoing Sequence Flows may be taken. A default flow must be specified at this point, there cannot be zero output flows. Merge: A process flow continues when it receives the first input signal from the input Sequence Flow. If other signals arrive after that, they are not used. | ||
Decision: This expression determines which output flow is taken from multiple Sequence Flow names. Merge: You specify a complex flow condition referencing incoming Sequence Flow names or process data coming into a gateway. This expression determines when the task starts. | ||
Fork: All Sequence Flows out of this gateway are taken. Join: This gate must receive input signals from all input Sequence Flows. The process flow does not continue until it receives all signals. |