Issue 14771: Beta 1 Spec: Section 10.3 Data [Data]: (bpmn2-rtf)
Source: Department of Veterans Affairs (Dr. Stephen White, steve.white(at)bookzurman.com)
Nature: Enhancement
Severity: Significant
Summary: Beta 1 Spec: Section 10.3 Data [Data]: If start of an activity is guarded by availability of input data, there should be some visible indication of this in the diagram

##Source: IBM (Stephen A. White, wstephe@us.ibm.com)
##Original Issue: http://www.osoa.org/jira/browse/BPMN-302
##Original Info: (Severity: Significant - Nature: Enhancement)

This is number 5 of 12 issues submitted by Bruce Silver

If start of an activity is guarded by availability of input data, there should be some visible indication of this in the diagram.  ("Modeling" means you don't need to see the non-diagram attributes).  It seems like BPMN 2.0 is trying to make data more a first class citizen, so this is needed.

Comments:
From: bruce created: Fri, 5 Dec 2008 17:29:56 -0600 (CST)
In a user task, it is understood that time can elapse between task ready and active, whereas in service task there is no delay.  So the temporal semantics are clear from the diagram.  The issue is when service task is guarded by data "availability" - whatever that implies.  If service task could incur delay between ready and active because of input data, this should be visible somehow in the diagram.


Resolution: 
Revised Text: 
Actions taken:
November 20, 2009: received issue
Discussion: 
This is a request for a new graphical element. The FTF agreed to defer this issue to a future RTF.
Disposition: Deferred
End of Annotations:=====
s is issue # 14771

[OMG 14771] Beta 1 Spec: Section 10.3 Data [Data]: If start of an activity is guarded by availability of input data, there should be some visible indication of this in the diagram

##Source: IBM (Stephen A. White, wstephe@us.ibm.com)
##Original Issue: http://www.osoa.org/jira/browse/BPMN-302
##Original Info: (Severity: Significant - Nature: Enhancement)

This is number 5 of 12 issues submitted by Bruce Silver

If start of an activity is guarded by availability of input data, there should be some visible indication of this in the diagram.  ("Modeling" means you don't need to see the non-diagram attributes).  It seems like BPMN 2.0 is trying to make data more a first class citizen, so this is needed.

Comments:
From: bruce created: Fri, 5 Dec 2008 17:29:56 -0600 (CST)
In a user task, it is understood that time can elapse between task ready and active, whereas in service task there is no delay.  So the temporal semantics are clear from the diagram.  The issue is when service task is guarded by data "availability" - whatever that implies.  If service task could incur delay between ready and active because of input data, this should be visible somehow in the diagram.