Issue 17528: Revision & clarification for interruption of looping / multi-instance sub-processes (bpmn2-rtf) Source: (, ) Nature: Revision Severity: Significant Summary: In Table 10.88 ­ End Event Types (page 248) it’s written: “Terminate ­ This type of End indicates that all Activities in the Process should be immediately ended. This includes all instances of multi-instances.” However, in 13.4.6 ­ End Events (page 443) it’s written: “For a ‘terminate’ End Event, the Sub-Process is abnormally terminated. In case of a multi-instance Sub-Process, only the affected instance is terminated—no other ongoing Sub-Process instances or higher-level Sub-Process or Process instances are affected.” So, it seems to be a contradiction: first it’s written all instances of multi-instances are terminated, but after it’s written only one instance is terminated. CLARIFICATION ============= Since the contradiction mentioned above, I think it’s also needed to clarify how many instances are terminated when a multi-instance Sub-Process is interrupted via Boundary Event or via Event Sub-Process. The specification also does not mention how the interruption of a looping Sub-Process should be handled: is only the current iteration interrupted (like the “continue” statement in software programming), or the whole loop is interrupted (like the “break” statement in software programming)? So, it’s needed to clarify this behavior for interruptions triggered via terminate End Event, Boundary Events and Event Sub-Processes. This issue is related to Issue #14824. Resolution: Revised Text: Actions taken: July 20, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 20 Jul 2012 08:38:15 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Andréomes da Silva Employer: mailFrom: andregs@gmail.com Terms_Agreement: I agree Specification: Business Process Model and Notation (BPMN) Section: 10.4.3, 13.4 FormalNumber: formal/2011-01-03 Version: 2.0 Doc_Year: 2011 Doc_Month: January Doc_Day: 03 Page: 248, 443 Title: Revision & clarification for interruption of looping / multi-instance sub-processes Nature: Revision Severity: Significant CODE: 3TMw8 B1: Report Issue Description: REVISION ============= In Table 10.88 ­ End Event Types (page 248) it.s written: .Terminate ­ This type of End indicates that all Activities in the Process should be immediately ended. This includes all instances of multi-instances.. However, in 13.4.6 ­ End Events (page 443) it.s written: .For a .terminate. End Event, the Sub-Process is abnormally terminated. In case of a multi-instance Sub-Process, only the affected instance is terminated.no other ongoing Sub-Process instances or higher-level Sub-Process or Process instances are affected.. So, it seems to be a contradiction: first it.s written all instances of multi-instances are terminated, but after it.s written only one instance is terminated. CLARIFICATION ============= Since the contradiction mentioned above, I think it.s also needed to clarify how many instances are terminated when a multi-instance Sub-Process is interrupted via Boundary Event or via Event Sub-Process. The specification also does not mention how the interruption of a looping Sub-Process should be handled: is only the current iteration interrupted (like the .continue. statement in software programming), or the whole loop is interrupted (like the .break. statement in software programming)? So, it.s needed to clarify this behavior for interruptions triggered via terminate End Event, Boundary Events and Event Sub-Processes. This issue is related to Issue #14824.