BPMN 2.1 RTF Avatar
  1. OMG Issue

BPMN21 — Wrong configuration of Event-Based Gateway

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

    i) Chapter/Section 10.5.6. Page 306. It says:
    “Event-Based Gateways are configured by having outgoing Sequence Flows target an Intermediate Event
    or a Receive Task in any combination (see Figure 10.116 and Figure 10.117) except that:

    • If Message Intermediate Events are used in the configuration, then Receive Tasks MUST NOT be used
      in that configuration and vice versa.”

    ii) Chapter/Section 10.5.
    Page 298: “A diverging Exclusive Gateway (Decision) ...”
    Page 300: “A diverging Inclusive Gateway (Inclusive Decision) …”
    Page 305: “The Event-Based Gateway represents a branching point in the Process where the alternative paths
    that follow the Gateway are based on Events that occur, rather than the evaluation of Expressions
    using Process data (as with an Exclusive or Inclusive Gateway).”

    iii) Chapter/Section 14.1.4. Page 478. Sub-section “Exclusive (Event-based) Decision Pattern”.
    Figure shows tree branches with one Message Intermediate Event, one Receive Task
    and one Timer Intermediate Event.


    According to Message Intermediate Events and Receive Tasks MUST NOT be used in the same configuration of an Event-Based Gateway. Nevertheless, in (iii) both are used in the same configuration.

    According to (ii) Exclusive and Inclusive Gateways are considered “decisions”, but not Event-Based Gateways.


    Modify Figure in Sub-section “Exclusive (Event-based) Decision Pattern”: use Message Intermediate Events or Receive Tasks, but not both.

    Name the Sub-section: “Exclusive (Event-based) Pattern”

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