-
Key: BPMN2-57
-
Legacy Issue Number: 14331
-
Status: closed
-
Source: Trisotech ( Mr. Denis Gagne)
-
Summary:
Reported by dga...@trisotech.com, Jul 29, 2009
In the last two structural specifications of page 244:
Should Event Sub-process be added to the exceptions that any other
elements must not have incoming Sequence Flow when a Start Event is used? -
Reported: BPMN 2.0b1 — Fri, 4 Sep 2009 04:00 GMT
-
Disposition: Resolved — BPMN 2.0
-
Disposition Summary:
The correction to the first structural specification was defined by the resolution of 14334. The remaining items are for the correction to the second structural
specification.
(a) Section 10.4.2 Start Event, page 215 (245 pdf), after first bullet on page: Add a second level bullet with the following text: "An exception to this is a Intermediate
Event, which MAY be without an incoming Sequence Flow (when attached to an Activity boundary)."
(b) Section 10.4.2 Start Event, page 215 (245 pdf), after first bullet on page: Add a second level bullet with the following text: "An exception to this is a catching Link
Intermediate Event, which is not allowed to have incoming Sequence Flow. See page 243 for more information on Link Intermediate Events."
(c) Section 10.4.2 Start Event, page 214 (244 pdf), after last bullet on page: Add a second level bullet with the following text: "An exception to this is an Event Sub-
Process, which is not allowed to have incoming Sequence Flow and will only be instantiated when its Start Event is triggered. See page 155 for more information on
Event Sub-Processes." -
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN2 — Page 244, section 10.4.2 Last two structural specifications for Start Event
- Key: BPMN2-57
- OMG Task Force: BPMN 2.0 FTF