Legacy Issue Number: 14739
Source: BPM Advantage Consulting ( Stephen White)
Since all activities have performers and priorities. it makes sense to be able to use the actual performer or priority of any activity in the definition of any other activity. E.g., the performer of this activity cannot be the same as that activity. Performers can do the work as in User Tasks, or just be stakeholders or authorizers, etc. for any activity (including sub-processes). Right now only User Activities have these instance attributes. Moving the attributes to the Activity level would allow other activities this capability.
Reported: BPMN 2.0b1 — Fri, 20 Nov 2009 05:00 GMT
Disposition: Resolved — BPMN 2.0
These instance attributes are defined for User Tasks only, as they are needed for different human interaction scenarios.
For other task types, e.g. Receive Task, Send Task, Service Task, Business Rule Task the value of having these instance attributes is not clear. E.g. It is not clear what
would be the Actual Owner of a Receive Task or a Send Task.
The proposal is to close this issue with no changes to the specification.
Disposition: Closed, No Change
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN2 — Beta 1: Section 10.2 Activities: Move User Task Instance Attributes to the higher level Activity element
- Key: BPMN2-181
- OMG Task Force: BPMN 2.0 FTF