Issue 10096: Inclusive Event-Based Decision (bpmn-ftf) Source: International Business Machines (Dr. Stephen White, wstephe@us.ibm.com sawscape@gmail.com) Nature: Uncategorized Issue Severity: 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. Resolution: Revised Text: Actions taken: August 7, 2006: received issue Discussion: Defer: While the Issue may be valid, it represents potentially significant modifications. Thus, this Issue will be deferred and handled by work on a later version of BPMN. End of Annotations:===== ubject: BPMN issue X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006 From: Stephen A White Date: Tue, 8 Aug 2006 16:10:51 -0700 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 7.0.1HF269 | June 22, 2006) at 08/08/2006 17:10:52, Serialize complete at 08/08/2006 17:10:52 BPMN Issue: Inclusive Event-Based Decision Description 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. To: bpmn-ftf@omg.org Subject: Proposed Resolution for Issue 10096 X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006 From: Stephen A White Date: Tue, 5 Dec 2006 08:15:23 -0500 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 7.0.2HF32 | October 17, 2006) at 12/05/2006 06:15:24, Serialize complete at 12/05/2006 06:15:24 This is intended for Ballot 5 Issue 10096: Inclusive Event-Based Decision? Description: 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. Suggested Resolution: Defer: While the Issue may be valid, it represents potentially significant modifications. Thus, this Issue will be deferred and handled by work on a later version of BPMN. Revised Text: None