BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — Persistent versus transient event trigger

  • Key: BPMN2-223
  • Legacy Issue Number: 14823
  • Status: closed  
  • Source: VDMbee ( Mr. Henk de Man)
  • Summary:

    Define for intermediate messages (intermediate event trigger) if the message should be persisted in the process scope when the intermediate message is not yet active.

    (See also workflow patterns from van der Aalst; e.g. http://www.workflowpatterns.com/evaluations/standard/index.php and
    http://www.workflowpatterns.com/patterns/control/new/wcp24.php
    ).

    It relates to e.g. the following on page 226 in the BPMN 2.0 Beta 1 specification:

    “If the Event is used to “catch” the Event Trigger, then the token will remain at the Event until the Trigger occurs (e.g., the Message is received).”

    Differentiation is required between whether one wants to persist (or "defer") the trigger, or whether one wants to "lose" the trigger when the process is not yet in state to react.

  • Reported: BPMN 2.0b1 — Wed, 25 Nov 2009 05:00 GMT
  • Disposition: Resolved — BPMN 2.0
  • Disposition Summary:

    This issue cannot be fixed in this FTF.
    Disposition: Closed, Out Of Scope

  • Updated: Fri, 6 Mar 2015 20:57 GMT