BPMN 2.1 RTF Avatar
  1. OMG Issue

BPMN21 — Revision & clarification for interruption of looping / multi-instance sub-processes

  • Key: BPMN21-333
  • Legacy Issue Number: 17528
  • Status: open  
  • Source: gmail.com ( Andre Gomes da Silva)
  • 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.

  • Reported: BPMN 2.0 — Fri, 20 Jul 2012 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT