BPMN 1.0 NO IDEA Avatar
  1. OMG Issue

BPMN — BPMN comment

  • Key: BPMN-4
  • Legacy Issue Number: 9121
  • Status: closed  
  • Source: Anonymous
  • Summary:

    BPMNOne point that need more precision in the BPMN specification is Inclusive Gateways behavior.
    The rule "When the Inclusive Gateway is used as a Merge, it will wait for (synchronize) all Tokens that have been produced upstream" is not clear at all.
    It can be applied in very simple situations (when a token is divided in several tokens when going out of an Inclusive Gateway, and merge at another Inclusive Gateway for example), but as no sense in more complex cases. As BPMN is very flexible and allows modeling of business processes that are not "block-structured" as opposed to BPEL, a more precise rule is needed for Inclusive Gateways.
    A discussion was opened by Petko Chobantonov on BPMN forum about this problem. He proposed another rule to clarify the Inclusive Gateway behavior but that led to nothing.

    Here is another comment:

    In the last version of the BPMN specification (Version 1.1 - July 31, 2005), a new rule was added on gateways (p 88):

    "If two or more Signals (Tokens) arrive to their respective Gates at the exact same time, then the Signal..."

    "exact same time" does not mean anything, and a rule like this has nothing to do in a "Notation" specification.

  • Reported: BPMN 1.0b1 — Mon, 20 Feb 2006 05:00 GMT
  • Disposition: Resolved — BPMN 1.0
  • Disposition Summary:

    No Data Available

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