Processes
| Spec Page | Spec Rule Text | RuleId |
|---|---|---|
87 |
Choreography Activities MUST NOT be included as a flowElement for a Process. |
|
239 |
There are seven (7) types of Start Events for top-level Processes in BPMN (see Table 10.84): None, Message, Timer, Conditional, Signal, Multiple, and Parallel. |
|
262 |
The Compensation Start Event MAY NOT be used for a top-level Process. |
|
238 |
If a Process is complex and/or the starting conditions are not obvious, then it is RECOMMENDED that a Start Event be used. |
|
246 |
If there is a Start Event, then there MUST be at least one End Event. |
|
238 |
If there is an End Event, then there MUST be at least one Start Event. |
|
251 |
In normal flow, the Escalation Intermediate Event raises an Escalation. Since this is a Throw Event, the arrowhead marker will be filled. |
|
251 |
In normal flow, this [Compensation] Intermediate Event indicates that compensation is necessary. Thus, it is used to "throw" the Compensation Event, and the Event marker MUST be filled. |
|
262 |
The catch Compensation Intermediate Event  MUST only be attached to the boundary of an Activity and, thus, MAY NOT be used in Normal Flow. |
|
250 |
Ten of the twelve Intermediate Events can be used in normal flow. Table 10.89 [Error and Cancel cannot be used]. |
|
258 |
The Intermediate Events with the following Triggers (EventDefinition) MAY be used in normal flow: None, Message, Timer, Escalation, Compensation, Conditional, Link, Signal, Multiple, and Parallel Multiple. Thus, the following MUST NOT: Cancel and Error. |
|
Decompose from above (258) |
Intermediate event with an Error event definition MUST NOT be used in normal flow. |
|
Decompose from above (258) |
Intermediate event with a Cancel event definition MUST NOT be used in normal flow. |
|
254 |
A catch Intermediate Error Event can only be attached to the boundary of an Activity, i.e., it MAY NOT be used in normal flow. |
|
261 |
The catch Cancel Intermediate Event  MUST only be attached to the boundary of a Transaction Sub-Process and, thus, MAY NOT be used in Normal Flow. |
|
266 |
There can be multiple source [throw] Link Events, but there can only be one target [catch] Link Event. |
|
258 |
If there is a source Link [Intermediate Event], there MUST be a matching target Link Intermediate Event (they have the same name). |
|
258 |
There MAY be multiple source Links for a single target Link. |
|
258 |
There MUST NOT be multiple target Links for a single source Link. |
|
261 |
The Cancel End Event MUST only be used within a Transaction Sub-Process and, thus, MAY NOT be used in any other type of Sub-Process or Process. |