Issue 14824: Continue versus terminate in loop (bpmn2-rtf)
Source: VDMbee (Mr. Henk de Man, hdman(at)vdmbee.com)
Nature: Enhancement
Severity: Significant
Summary: Introduction of end type break within a loop construct (continue construct is already there, implemented by the terminate end type which can be used inside a loop (multi instance activity) to end the loop).” 



This relates to what is e.g. said on page 407: “For a “terminate” End Event, the Sub-Process is abnormally terminated. In case of a multi-instance Activity, only the affected instance is terminated.”

So, differentation is required between the two modes of getting out of the loop.
Resolution: 
Revised Text: 
Actions taken:
November 25, 2009: received issue
Discussion: 
The FTF Team is not able to allocate time to reach resolution, so we will defer this issue.
Disposition: Deferred
End of Annotations:=====

m: webmaster@omg.org
Date: 25 Nov 2009 05:36:35 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:          Henk de Man
Company:       Cordys
mailFrom:      hdman@cordys.com
Notification:  Yes
Specification: BPMN
Section:       14.4.6
FormalNumber:  dtc/2009-08-14
Version:       2.0 (Beta 1)
RevisionDate:  8/14/2009
Page:          407
Title:         Continue versus terminate in loop
Nature:        Enhancement
Severity:      Significant
test:          3qw8
B1:            Report Issue


Description:


Required: Introduction of end type continue within a loop construct (continue construct is already there, implemented by the terminate end type which can be used inside a loop (multi instance activity) to end the loop).


This relates to what is e.g. said on page 407: .For a .terminate. End Event, the Sub-Process is abnormally terminated. In case of a multi-instance Activity, only the affected instance is terminated..

So, differentation is required between the two modes of getting out of the loop.