BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — Complex gateway merging rule in choreography too restrictive

  • Key: BPMN2-118
  • Legacy Issue Number: 14655
  • Status: closed  
  • Source: NIST ( Conrad Bock)
  • Summary:

    The rule fo merging complex gateway in choreography is

    "In order to enforce the synchronizing merge of the Gateway, the
    senders or receivers Choreography Activities preceding the Gateway
    need to be the same Participant. This ensures that the merge can be
    enforced."

    but if the sender of the activity after the gateway participates in the
    activties before the gateway, and has access to the complex decision
    data, then it has everything needed to perform the synchronization.

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

    The quote in the issue is from the inclusive gateway, rather than the
    complex merge.
    In the Choreography chapter, in section Gateways, subsection Inclusive
    Gateway, under the third paragraph, first bullet, second subbullet (the
    one beginning "Merge:"), in the sentence immediately after the colon
    (the one beginning "In order to enforce"), replace the portion of the
    sentence after the comma with:
    the sender of the Choreography Activity after the Gateway must
    participate in the Choreography Activities immediately preceding the
    gateway.
    In the Choreography chapter, in section Gateways, subsection Inclusive
    Gateway, in the paragraph just above the first figure, third sentence,
    replace the portion of the sentence after the comma with:
    the initiator of Choreography Activities immediately following the
    Gateway participates in the Choreography Activities immediately
    preceding the Gateway.
    Disposition: Resolved

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