Legacy Issue Number: 11601
Source: NIST ( Conrad Bock)
In clause 9.7.2 and 10.1.4, it is stated that a data object artifact can be associated with a (Sequence or Message) Flow.
But the meaning of association with a Sequence Flow is not
In Figure 9.40 there is an example of an association of a data object to a Sequence Flow between two Activities. Is such an association only permitted when the Flow is between two Activities? Is it permitted when the flow is between an Activity and a Gateway?
For example, could Figure 9.40 have two activities on the right, with an exclusive data gateway (decision) routing the data object to one or the other under certain conditions?
Is there a meaning to associating the data object with a Sequence Flow that terminates in an Event (throw or catch)?
When the flow originates from an Activity, the data object is an output of that Activity that is available at the time of the flow. When the flow terminates in an Activity, the data object is an input to that Activity that is available at the time the Activity starts. (This is the conclusion to be drawn from the current text. But these statements are independent of what is on the other end.)
If the flow originates from a gateway or event, BPMN assigns no meaning to the association with respect to that end, but a conforming tool may.
If the flow terminates in a gateway or event, the data object is an "input" artifact that is available when the Gateway decision is made, the Event is thrown, or the wait for the Event begins. The artifact, or the knowledge of its availability, may be used in making the Gateway decision or throwing or handling the Event.
The preferred representation of a data object "flowing" past a gateway or event is to show two (or more) associations:
output from the originating activity and input to the activity (or activities) that use the artifact. (And there should be an example of this.)
Reported: BPMN 1.1 — Tue, 9 Oct 2007 04:00 GMT
Disposition: Resolved — BPMN 1.2
Close, No Change: This issue is out of scope for the RTF and will be addressed by the response to
the BPMN 2.0 RFP.
Revised Text: None
Disposition: Closed, deferred
Updated: Wed, 11 Mar 2015 01:53 GMT