Start Events
| Spec Page | Spec Rule Text | RuleId |
|---|---|---|
244 |
A Start Event MUST NOT be a target for Sequence Flows; it MUST NOT have incoming Sequence Flows. |
|
244 |
An exception to this is when a Start Event is used in an Expanded Sub-Process and is attached to the boundary of that Sub-Process. In this case, a Sequence Flow from the higher-level Process MAY connect to that Start Event in lieu of connecting to the actual boundary of the Sub-Process. |
|
244 |
A Start Event MUST be a source for Sequence Flow. |
|
245 |
A Start Event MUST NOT be a source for Message Flow; it MUST NOT have outgoing Message Flows. |
|
42 (Deduced from Table 7.4) |
The Trigger attribute of the Start Event MUST be set to Message or Multiple if there are any incoming Message Flows. |
|
42 (Deduced from Table 7.4) |
The Trigger attribute of the Start Event MUST be set to Multiple if there is more than one (1) incoming Message Flows. |
|
244 |
The conditionExpression attribute for all outgoing Sequence Flows [of a Start Event] MUST be set to None. |