Business Process Model and Notation Avatar
  1. OMG Specification

Business Process Model and Notation — Open Issues

  • Acronym: BPMN
  • Issues Count: 3
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
BPMN11-92 Message flows in and out of independent sub-processes BPMN 1.0b1 open
BPMN11-91 BPMN Issue: Exclusive Gateway Merging BPMN 1.0b1 open
BPMN11-90 Update definition of merging behavior of Exclusive Data-Based Gateway BPMN 1.0b1 open

Issues Descriptions

Message flows in and out of independent sub-processes

  • Key: BPMN11-92
  • Legacy Issue Number: 10139
  • Status: open  
  • Source: me.com ( Frank McCabe)
  • Summary:

    Where an activity represents an invocation of an independent
    subprocess, the spec does not state how to bin any incoming and
    outgoing message flows to the sub-process. It does state how to bind
    information (input and output sets) but not messages.
  • Reported: BPMN 1.0b1 — Thu, 24 Aug 2006 04:00 GMT
  • Updated: Wed, 11 Mar 2015 01:55 GMT

BPMN Issue: Exclusive Gateway Merging

  • Key: BPMN11-91
  • Legacy Issue Number: 9615
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    The BPMN 1.0 version of the Exclusive Gateway merging (either data or event Gateways) acts as a "pass through" for any Tokens that arrive. This means that there is no "exclusiveness" to the merging as the name of the Gateway would imply. A "discriminator" merging that allows the first Token through and stops any further (parallel) Tokens is a business pattern that cannot be currently modeled. This functionality should either replace the current merging behavior or be added to the behavior.

  • Reported: BPMN 1.0b1 — Fri, 28 Apr 2006 04:00 GMT
  • Updated: Wed, 11 Mar 2015 01:55 GMT

Update definition of merging behavior of Exclusive Data-Based Gateway

  • Key: BPMN11-90
  • Legacy Issue Number: 9410
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    Update the definition of the merging behavior of the Exclusive Data-Based Gateway. Currently, the Gateway just passes all Tokens through. The behavior should be changed to be exclusive in that it will allow the first Token to arrive through the Gateway, but ignore/consume all other Tokens from the same Token family.

  • Reported: BPMN 1.0b1 — Thu, 2 Mar 2006 05:00 GMT
  • Updated: Wed, 11 Mar 2015 01:55 GMT