Event Gateways
| Spec Page | Spec Rule Text | RuleId |
|---|---|---|
296 |
An Event Gateway MUST have two or more outgoing Sequence Flow |
|
297 |
Event-Based Gateways are configured by having outgoing Sequence Flows target a [Catch] Intermediate Event or a Receive Task in any combination except that: |
|
297 |
If Message Intermediate Events are used in the configuration of an Event-Based Gateway, then Receive Tasks MUST NOT be used in that configuration and vice versa. |
|
297 |
Receive Tasks used in an Event Gateway configuration MUST NOT have any attached Intermediate Events. |
|
297 |
Only the following Intermediate Event triggers are valid: Message, Signal, Timer, Conditional, and Multiple (which can only include the previous triggers). Thus, the following Intermediate Event triggers are not valid: Error, Cancel, Compensation, and Link. |
|
Decomposed from above () |
Error Intermediate Event cannot be used to configure an Event Based Gateway |
|
Decomposed from above () |
Cancel Intermediate Event cannot be used to configure an Event Based Gateway. |
|
Decomposed from above () |
Compensation Intermediate Event cannot be used to configure an Event Based Gateway |
|
Decomposed from above () |
Link Intermediate Event MUST NOT be used to configure an Event Based Gateway. |
|
297 |
Target elements in an Event Gateway configuration MUST NOT have any addition incoming Sequence Flow (other than that from the Event Gateway). |
|
298 |
In order for an Event Gateway to instantiate a Process, it MUST not have any incoming Sequence Flows. |
|
349 |
On the right side of the [Event Based] Gateway: either The senders MUST to be the same; or The receivers MUST to be the same. |
|
Deducted |
Event based gateway in choreography are configured using Choreography Activities, catching Signal intermediate events and Timer Intermediate events. No other elements should be used. |
|
349 |
Message Intermediate Events MUST NOT be used in the Event-Based Gateway [within choreography]. |
|
349 |
Timer Intermediate Events MAY be used [in the Event Based Gateway within choreography], but they restrict the participation in the Gateway |
|
349 |
For relative timers: All Participants on the right side of the Gateway MUST be involved in the Choreography Activity that immediately precedes the Gateway |
|
349 |
For absolute timers (full time/date): All Participants on the right side of the Gateway MUST be involved in the Choreography Activity that immediately precedes the Gateway. |
|
349 |
No other [other than Timer and Signal] types of Intermediate Events are allowed [in Event Based Gateway within Choreography]. |