BPMN 2.1 RTF Avatar
  1. OMG Issue

BPMN21 — None Intermediate Event: “catch” or “throw”

  • Key: BPMN21-233
  • Legacy Issue Number: 15740
  • Status: open  
  • Source: craftware.net ( Eduardo Jara)
  • Summary:

    Description:

    ANTECEDENTS:
    i) Chapter/Section 10.4.4. Page 259. Table 10.89. Row “None”. It says:
    “The None Intermediate Event is only valid in normal flow, i.e., it MAY NOT be used on the boundary of an Activity. Although there is no specific trigger for this Event, it is defined as throw Event.”

    ii) Chapter/Section 10.4.5. Page 269. Table 10.93. Row “None”.
    None Intermediate Event is shown as a throw Event

    iii) Chapter/Section 10.4.5. Page 280. It says:
    “There are three (3) variations of None Events: a Start Event, a catch Intermediate Event, and …”

    “The catch None Intermediate Event MUST only be used in normal flow and, thus, MAY NOT be attached to the boundary of an Activity.”

    COMMENTS:

    In and (ii) None Intermediate Event is defined as a throw Event, but in (iii) it is considered to be a catch Event

    SUGGESTIONS:

    It seems that it is not important which type (throw or catch) would be chosen, but it is necessary to define one and be consistent in its use.

    Note: see Issue 15687

  • Reported: BPMN 2.0 — Fri, 15 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT