Issue 9570: BPMN spec doesn't include join condition (bpmn-ftf) Source: Capability Measurement (Mr. Karl Frank, Karl.Frank@ngc.com karl.frank@ngc.com karl.karolus@gmail.com karl.frank@capabilitymeasurement.com) Nature: Uncategorized Issue Severity: Summary: each action may contain join condition and have associated 'suppressJoinFailure' flag. BPMN spec doesn't include join condition at all and puts suppressJoinFailure to the Process level only. Borland created complex structures to reflect behavior of related BPEL elements to enable generation. Resolution: Revised Text: Actions taken: April 13, 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:===== s is issue # 9570 BPMN spec doesn't include join condition each action may contain join condition and have associated 'suppressJoinFailure' flag. BPMN spec doesn't include join condition at all and puts suppressJoinFailure to the Process level only. Borland created complex structures to reflect behavior of related BPEL elements to enable generation. To: bpmn-ftf@omg.org Subject: Proposed Resolution for Issue 9570 X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006 From: Stephen A White Date: Fri, 10 Nov 2006 21:43:03 -0800 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 7.0.1HF346 | August 4, 2006) at 11/10/2006 22:43:03, Serialize complete at 11/10/2006 22:43:03 This is intended for Ballot 5 (the first ballot of the FTF V2) Issue 9570: BPMN spec doesn't include join condition Description: each action may contain join condition and have associated 'suppressJoinFailure' flag. BPMN spec doesn't include join condition at all and puts suppressJoinFailure to the Process level only. Borland created complex structures to reflect behavior of related BPEL elements to enable generation. 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