BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — Page 204, Table 10-26, MultiInstance Activity: Potential error and clarification regarding **BehaviorEventRef

Open Closed All
  • Key: BPMN2-90
  • Legacy Issue Number: 14540
  • Status: closed  
  • Source: Trisotech ( Mr. Denis Gagne)
  • Summary:

    Page 204, Table 10-26, There seems to be an error in providing an attribute called noneBehaviorEventRef, it should be allBehaviorEventRef....? Futhermore a complexBehaviorEventRef attribute would be missing....?

    But why do we need multiple ***BehaviorEventRef attributes? Couldn't we just have a BehaviorEventRef attribute that is used for either one, all or complexe?

  • Reported: BPMN 2.0b1 — Thu, 8 Oct 2009 04:00 GMT
  • Disposition: Resolved — BPMN 2.0
  • Disposition Summary:

    There is no issue. The questions in the issue description probably arose from a misunderstanding of the "complex" MI behavior, which refers to multiple event
    descriptions and not necessarily a single one as assumed by the reporter. When behavior is complex, we have multiple event refs, so we cannot unify with the other two
    options. "none" and "one" could indeed be unified; but it would be clearer not to unify.
    Disposition: Closed, No Change
  • Updated: Fri, 6 Mar 2015 20:57 GMT