Choreographies
| Spec Page | Spec Rule Text | RuleId |
|---|---|---|
87 |
Activities, Data Associations, and Data Objects MUST NOT be included as a flowElement for a Choreography. |
|
339 |
Prohibited/Restricted Use of Start Events in Choreography |
|
Table11.6 (340) |
Types of Event: Message Usage In choreography? No |
|
Table11.6 (340) |
Types of Event: Escalation Usage In choreography? No |
|
Table11.6 (340) |
Types of Event: Error Usage In choreography? No |
|
Table11.6 (340) |
Types of Event: Compensation Usage In choreography? No |
|
340 |
Prohibited/Restricted Use of Intermediate Events in Choreography |
|
Table11.7 (340) |
Types of Event: Message: in Normal Flow Usage In choreography? No |
|
Table11.7 (340) |
Types of Event: Cancel: in Normal Flow Usage In choreography? No |
|
Table11.7 (340) |
Types of Event: Compensation: in Normal Flow Usage In choreography? No |
|
Table11.7 (340) |
Types of Event: Escalation: Used in Normal Flow Usage In choreography? No |
|
Table11.7 (340) |
Types of Event: Message: Use in Event Gateway Usage In choreography? No |
|
Table11.7 (340) |
Types of Event: Signal: in Normal Flow Usage In choreography? Yes. Only Catch Events can be used |
|
Table11.7 (340) |
Types of Event: Multiple: in Normal Flow Usage In choreography? Yes. But they can only be a collection of valid Catch Events. |
|
Table11.7 (340) |
Type of Event: Error in normal Flow. No (based on the fact they can never be used in normal flow) |
|
342 |
Type of event: Link in Normal Flow: Yes. These types of Events merely create a virtual Sequence Flows. Thus, as long as a Sequence Flow between two elements is valid (and within a Choreography Process level), then a pair of Link Events can interrupt that Sequence Flow. |
|
252 |
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. |
|
Table11.7 (340) |
Prohibited/Restricted Use of Boundary Intermediate Events in Choreography |
|
Table11.7 (340) |
Types of Event: None: Attached to Activity boundary Usage In choreography? No |
|
Table11.7 (340) |
Types of Event: Error: Attached to Activity boundary Usage In choreography? No |
|
Table11.7 (340) |
Types of Event: Escalation: Attached to Activity boundary Usage In choreography? No |
|
Table11.8 (343) |
Prohibited/Restricted Use of End Events in Choreography |
|
Table11.8 (343) |
Types of Event: Message Usage In choreography? No |
|
Table11.8 (343) |
Types of Event: Escalation Usage In choreography? No |
|
Table11.8 (343) |
Types of Event: Error Usage In choreography? No |
|
Table11.8 (343) |
Types of Event: Cancel Usage In choreography? No |
|
Table11.8 (343) |
Types of Event: Compensation Usage In choreography? No |
|
Table11.8 (343) |
Types of Event: Signal Usage In choreography? No |
|
Table11.8 (343) |
Types of Event: Multiple Usage In choreography? No |
|
411 |
The source [sourceElement] and target [targetElement] of a BPMNEdge can never be a BPMNShape with participantBandKind set (i.e. only Choreography Activity can be source or target of the BPMNEdge not the Participant Bands). |
|
410 |
The source |
target of a BPMNEdge should be redefined only two cases: when the redefined source |
target is a shape referring a BPMN element containing the original source |
target element that is not currently displayed and when the edge represents a data association. |