1. OMG Issue

BPMN11 — Do artifact flows affect execution

  • Key: BPMN11-61
  • Legacy Issue Number: 10339
  • Status: closed  
  • Source: NIST ( Conrad Bock)
  • Summary:

    Do artifact flows affect execution? Table 8.2 (BPD Core Element) says: Data Objects are considered Artifacts because they do not have any direct effect on the Sequence Flow or Message Flow of the Process, but they do provide information about what activities require to be performed and/or what they produce. Not sure, but the above seems to imply that artifact flows do not affect execution (it does not affect sequencing or messaging). Compare Table 9.10 (Common Activity Attributes): [Input: for InputSets only] Inputs (1-n) : Artifact One or more Inputs MUST be defined for each InputSet. An Input is an Artifact, usually a Document Object. InputSets (0-n) : Input The InputSets attribute defines the data requirements for input to the activity. Zero or more InputSets MAY be defined. uEach InputSet is sufficient to allow the activity to be performed (if it has first been instantiated by the appropriate signal arriving from an incoming Sequence Flow). which seems to imply an execution semantics ("Each InputSet is sufficient to allow the activity to be performed").

  • Reported: BPMN 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — BPMN 1.1
  • Disposition Summary:

    Close, No Change: The answer to the question is that Data Objects can affect the performance of
    individual activities. However, they do not affect the operational semantics of a BPMN diagram—in terms of when and which activities will be performed. This is determined by the Sequence Flow and

  • Updated: Fri, 6 Mar 2015 20:57 GMT