BPMN 1.1 MAILINGLIST Avatar
  1. OMG Issue

BPMN11 — Inclusive Event-Based Decision

  • Key: BPMN11-56
  • Legacy Issue Number: 10096
  • Status: closed  
  • Source: Department of Veterans Affairs ( Stephen White)
  • Summary:

    We may need a way to model more general logic patterns for incoming events. For example, in response to an RFQ, a supplier may send either a decline, or a quote and (as a separate message) terms & conditions. The logic pattern for this use case is

    Decline XOR ( Quote AND Terms )

    If the Decline is accompanied by a memo giving reasons, then the logic becomes

    ( Decline AND Memo ) XOR ( Quote AND Terms )

    We want to open up three event receivers initially (four in the second case). Then, as a Quote arrives for example, we want to close the receives for Decline and Memo — since we don't expect those any longer — but keep the receive for Terms & Conditions open. When those have arrived as well, the inclusive event-based gateway is complete.

  • Reported: BPMN 1.0b1 — Mon, 7 Aug 2006 04:00 GMT
  • Disposition: Resolved — BPMN 1.1
  • Disposition Summary:

    Suggested Resolution:
    Close, No Change: This issue is out of scope for the RTF and will be addressed by the response to
    the BPMN 2.0 RFP.
    Revised Text: None
    Disposition: Closed, deferred

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