-
Key: BPMN2-233
-
Legacy Issue Number: 14869
-
Status: closed
-
Source: BPM Advantage Consulting ( Dr. Stephen White)
-
Summary:
Choreographies contain Message Flow. The CallChoreographyActivity will call another Choreography or a GlobalChoreographyTask, both of which have there own Message Flow. There are similar relationships to Participant. A CallChoreographyActivity has a ParticipantAssociation, so it should also have a MessageFlowAssociation or should not have the ParticipantAssociation.
-
Reported: BPMN 2.0b1 — Wed, 16 Dec 2009 05:00 GMT
-
Disposition: Resolved — BPMN 2.0
-
Disposition Summary:
The Message Flow within the called Choreography will not be used or interact within the calling Choreography, so no mapping is required. Thus, there is no change
required to the specification.
Disposition: Closed, No Change -
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN2 — Does CallChoreography need a MessageFlowAssociation?
- Key: BPMN2-233
- OMG Task Force: BPMN 2.0 FTF