Issue 15760: Wrong configuration of Event-Based Gateway (bpmn2-rtf)
Source:  (, )
Nature: Revision
Severity: Significant
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.



COMMENTS:


According to (i) 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.



SUGGESTIONS:


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”
Resolution: 
Revised Text: 
Actions taken:
October 18, 2010: received issue
Discussion: 


End of Annotations:=====

m: webmaster@omg.org
Date: 17 Oct 2010 21:41:12 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Eduardo Jara
Employer:        
mailFrom:        ejara@craftware.net
Terms_Agreement: I agree
Specification:   BPMN 2.0 Beta 2
Section:         14.1.4
FormalNumber:    dtc/2010-06-05
Version:         2.0
Doc_Year:        2010
Doc_Month:       June
Doc_Day:         Day
Page:            478
Title:           Wrong configuration of Event-Based Gateway
Nature:          Revision
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


ANTECEDENTS:


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.



COMMENTS:


According to (i) 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.



SUGGESTIONS:


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.