BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — Default execution semantics for an activity with multiple incoming branches needs to be clarified

Open Closed All
  • Key: BPMN2-208
  • Legacy Issue Number: 14795
  • Status: closed  
  • Source: Oracle ( Vishal Saxena)
  • Summary:

    The current execution semantics apparently implies that the said activity with two incoming connections will be executed twice. Instead it should be a merge semantics that is the activity is executed once when token arrives on both branches.
  • Reported: BPMN 2.0b1 — Tue, 24 Nov 2009 05:00 GMT
  • Disposition: Resolved — BPMN 2.0
  • Disposition Summary:

    The proposal in the issue description is in conflict with start events on the boundary of a sub-process as explained above and also conflicts compatibility with BPMN
    1.1. Thus, we propose to close with no change.
    Disposition: Closed, No Change
  • Updated: Fri, 6 Mar 2015 20:57 GMT