Issue 19166: Allowable start events for event sub-process inconsistently defined (bpmn2-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: There is an apparent conflict in the specification concerning the permissible Start Event types for an Event Sub-Process. On Page 174, the specification states: "The Start Event of an Event Sub-Process MUST have a defined trigger. The Start Event trigger (EventDefinition) MUST be from the following types: Message, Error, Escalation, Compensation, Conditional, Signal, and Multiple." This enumeration excludes the Timer and Parallel event types. This specification appears inconsistent with the restriction on Page 241, which additionally allows Timer and Parallel event types for the Start Event: "A Start Event can also initiate an inline Event Sub-Process (see page 174). In that case, the same Event types as for boundary Events are allowed (see Table 10.86), namely: Message, Timer, Escalation, Error, Compensation, Conditional, Signal, Multiple, and Parallel." It is consequently unclear whether Timer and Parallel events may be the Start Event in an Event Sub-Process. Resolution: Revised Text: Actions taken: December 23, 2013: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 23 Dec 2013 13:44:16 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Devin Fensterheim Employer: mailFrom: drf_@outlook.com Terms_Agreement: I agree Specification: Business Process Model and Notation (BPMN), v2.0.1 Section: 10.3.5 FormalNumber: formal/2013-09-03 Version: 2.0.1 Doc_Year: 2013 Doc_Month: September Doc_Day: 03 Page: 174 Title: Allowable start events for event sub-process inconsistently defined Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Remote Name: c-68-50-239-241.hsd1.md.comcast.net Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 Time: 01:44 PM Description: There is an apparent conflict in the specification concerning the permissible Start Event types for an Event Sub-Process. On Page 174, the specification states: "The Start Event of an Event Sub-Process MUST have a defined trigger. The Start Event trigger (EventDefinition) MUST be from the following types: Message, Error, Escalation, Compensation, Conditional, Signal, and Multiple." This enumeration excludes the Timer and Parallel event types. This specification appears inconsistent with the restriction on Page 241, which additionally allows Timer and Parallel event types for the Start Event: "A Start Event can also initiate an inline Event Sub-Process (see page 174). In that case, the same Event types as for boundary Events are allowed (see Table 10.86), namely: Message, Timer, Escalation, Error, Compensation, Conditional, Signal, Multiple, and Parallel." It is consequently unclear whether Timer and Parallel events may be the Start Event in an Event Sub-Process.