Issue 17047: Incomming sequence flow at start event (bpmn2-rtf)
Source: University of Applied Sciences Dresden (Mr. Michael Gruenert, nobody)
Nature: Revision
Severity: Significant
Summary: An interesting rule (page 245):
‘A Start Event MUST NOT be a target for Sequence Flows; it MUST NOT have incoming Sequence Flows. An exception to this is when a Start Event is used in an Expanded Sub-Process and is attached to the boundary of that Sub-Process. In this case, a Sequence Flow from the higher-level Process MAY connect to that Start Event in lieu of connecting to the actual boundary of the Sub-Process.’


I never found a tool who implements this rule. On page 261 a ‘Boundary Start event’ does not exist. Only Intermediate Events are of type ‘boundary’ (interrupting/non-interrupting). Or interrupting/non-interrupting Start Events for an Event-Sub-Process (but they are not of type ‘boundary’).

-> is it ok to remove this exception?
Resolution: 
Revised Text: 
Actions taken:
January 24, 2012: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Michael GrüEmployer:        T-Systems-MMS / HTW-Dresden
mailFrom:        michael.gruenert@informatik.htw-dresden.de / gruenert@live.de / michael.gruenert@t-systems-mms.com
Terms_Agreement: I agree
Specification:   Business Process Model and Notation  (BPMN)
Section:         10.4
FormalNumber:    formal/2011-01-03
Version:         2.0
Doc_Year:        2011
Doc_Month:       January
Doc_Day:         03
Page:            538
Title:           Incomming sequence flow at start event
Nature:          Revision
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


An interesting rule (page 245):
.A Start Event MUST NOT be a target for Sequence Flows; it MUST NOT have incoming Sequence Flows. An exception to this is when a Start Event is used in an Expanded Sub-Process and is attached to the boundary of that Sub-Process. In this case, a Sequence Flow from the higher-level Process MAY connect to that Start Event in lieu of connecting to the actual boundary of the Sub-Process..


I never found a tool who implements this rule. On page 261 a .Boundary Start event. does not exist. Only Intermediate Events are of type .boundary. (interrupting/non-interrupting). Or interrupting/non-interrupting Start Events for an Event-Sub-Process (but they are not of type .boundary.).

-> is it ok to remove this exception?