Choreographies

333

The Participant Band of the Participant that does not initiate the interaction MUST be shaded with a light fill.

335

A Choreography Task is a rounded corner rectangle that MUST be drawn with a single line.

335

The use of text, color, size, and lines for a Choreography Task MUST follow the rules defined in Section “Use of Text, Color, Size, and Lines in a Diagram” on page 41.

335

If the Message [on the Choreography Task] is the initiating Message of the Choreography Task, then the Message icon MUST be unfilled.

335

If the Message [on the Choreography Task] is a return Message for the Choreography Task, then the Message icon MUST have a light fill.

335

A Choreography Task MAY have only one of the three (3) markers at one time

336

The marker for a Choreography Task that is a standard loop MUST be a small line with an arrowhead that curls back upon itself. The loopType of the Choreography Task MUST be Standard.

336

The marker for a Choreography Task that is parallel multi-instance MUST be a set of three vertical lines. The loopType of the Choreography Task MUST be MultiInstanceParallel.

336

The marker for a Choreography Task that is sequential multi-instance MUST be a set of three horizontal lines. The loopType of the Choreography Task MUST be MultiInstanceSequential.

337

The marker for a Choreography Task that is multi-instance [a participant] MUST be a set of three vertical lines

337

The marker that is present MUST be centered at the bottom of the Participant Band of the shape.

337

The width of the Participant Band will be expanded to contain both the name of the Participant and the multi-instance marker.

338

The [Choreography] Sub-Process marker MUST be a small square with a plus sign (+) inside. The square MUST be positioned at the bottom center of the Sub-Process Name Band within the shape.

338

The Participant Band of the Participant that does not initiate the interaction MUST be shaded with a light fill.

341

A Sub-Choreography is a rounded corner rectangle that MUST be drawn with a single thin line.

341

The use of text, color, size, and lines for a Sub-Choreography MUST follow the rules defined in Section "Use of Text, Color, Size, and Lines in a Diagram" on page 41.

341

However, each Participant Band that is added [on a Sub-Choreography] MUST be added to the upper and lower sections of the Sub-Choreography in an alternative manner.

341

A Sub-Choreography MAY have only one of the three (3) markers at one time.

341

The marker for a Sub-Choreography that is a standard loop MUST be a small line with an arrowhead that curls back upon itself. The loopType of theSub-Choreography MUST be Standard.

341

The marker for a Sub-Choreography that is parallel multi-instance MUST be a set of three vertical lines. The loopType of the Sub-Choreography MUST be MultiInstanceParallel.

341

The marker for a Sub-Choreography that is sequential multi-instance MUST be a set of three horizontal lines. The loopType of the Sub-Choreography MUST be MultiInstanceSequential.

341

The marker that is present MUST be centered at the bottom of the Sub-Process Name Band of the shape.

342

The marker for a Sub-Choreography [Participant] that is multi-instance MUST be a set of three vertical lines.

342

The marker that is present MUST be centered at the bottom of the Participant Band of the shape.

342

The width of the Participant Band will be expanded to contain both the name of the Participant and the multi-instance marker.

343

If the Call Choreography calls a Global Choreography Task, then the shape will be the same as a Choreography Task, but the boundary of the shape will MUST have a thick line.

343

If the Call Choreography calls a Choreography, then there are two (2) options:

343

The details of the called Choreography can be hidden and the shape will be the same as a collapsed Sub-Choreography, but the boundary of the shape MUST have a thick line.

343

The details of the called Choreography can be shown and the shape will be the same as an expanded Sub-Choreography, but the boundary of the shape MUST have a thick line.

352

Types of Event: Escalation: Attached to Activity boundary Usage In choreography? No

351

The Intermediate Event has to be attached to the Participant Band of the receiver of the Message (since it is a catch Event)

352

Types of Event: Cancel: Attached to Activity boundary Usage In choreography? Yes

352

They [cancel attached event] would be attached to the Choreography Activity on the Participant Band that is receiving the Cancel

351

The sender of the message has to be the other Participant of the Choreography Task.

355

To create an enforceable Choreography, the [Exclusive] Gateway Conditions MUST be formal Condition Expressions; however:

355

The data used for [Exclusive] Gateway Conditions MUST have been in a Message that was sent prior to (upstream from) the Gateway.

355

More specifically, all Participants that are directly affected by the [Exclusive] Gateway MUST have either sent or received the Message(s) that contained the data used in the Conditions.

355

Furthermore, all these Participants MUST have the same understanding of the data. That is, the actual values of the data cannot selectively change after a Participant has seen a Message. Changes to data during the course of the Choreography MUST be visible to all the Participants affected by the Gateway.

355

The initiating Participants of the Choreography Activities that follow the [Exclusive] Gateway MUST have sent or received the Message that provided the data upon which the decision is made.

362

The data used for [an Inclusive] Gateway [in a choreography] Conditions MUST have been in a Message that was sent prior to (upstream from) the Gateway.

362

More specifically, all Participants that are directly affected by the [Inclusive] Gateway MUST have either sent or received the Message(s) that contained the data used in the Conditions.

362

Furthermore, all these Participants MUST have the same understanding of the data. That is, the actual values of the data cannot selectively change after a Participant has seen a Message. Changes to data during the course of the Choreography MUST be visible to all the Participants affected by the [Inclusive] Gateway.

392

A BPMNPlane can only reference a BaseElement of the types: Process, SubProcess, AdHocSubProcess, Transaction, Collaboration, Choreography or SubChoreography.

392

Only positive coordinates are allowed for diagram elements that are nested in a BPMNPlane.

393

The bounds of a BPMNShape are always relative to that plane’s origin point and are REQUIRED to be positive coordinates.

395

The source or target definition should only be present if the edge is depicted between a different source or target than the one referenced by the BPMN model element of the BPMNEdge. Only the different source or target is REQUIRED. Both attributes should be present only if both are different.

395

The waypoints of BPMNEdge are always relative to that plane’s origin point and are REQUIRED to be positive coordinate