Issue 15687: None Events not for catch Intermediate Event (bpmn2-rtf)
Source:  (, )
Nature: Enhancement
Severity: Minor
Summary: The following text is from page 280:
There are three (3) variations of None
Events: a Start Event, a catch Intermediate Event, and an End Event (see Figure 10.91).


The catch None Intermediate Event MUST only be used in normal flow and, thus, MAY NOT be attached to the boundary of an Activity.


However, according to Table 10.93 and the former text, a None-Trigger is allowed for a Start Event, End Event and for a throw Intermediate Event but not for a catch Intermediate Event.

Resolution: resolved
Revised Text: 
Actions taken:
October 7, 2010: received issue
April 25, 2011: closed issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 07 Oct 2010 07:38:31 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Christine Natschlär
Employer:        
mailFrom:        Christine.Natschlaeger@scch.at
Terms_Agreement: I agree
Specification:   Business Process Model and Notation (BPMN)
Section:         10.4.5
FormalNumber:    dtc/2010-06-05
Version:         2.0
Doc_Year:        2010
Doc_Month:       June
Doc_Day:         05
Page:            280
Title:           None Events not for catch Intermediate Event
Nature:          Enhancement
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


The following text is from page 280:
There are three (3) variations of None
Events: a Start Event, a catch Intermediate Event, and an End Event (see Figure 10.91).


The catch None Intermediate Event MUST only be used in normal flow and, thus, MAY NOT be attached to the boundary of an Activity.


However, according to Table 10.93 and the former text, a None-Trigger is allowed for a Start Event, End Event and for a throw Intermediate Event but not for a catch Intermediate Event.


Best regards,
Christine Natschlär