Bernard Szlachta: /* Common Activity Attributes ⌘ */

2012-11-22T09:15:10Z

Common Activity Attributes ⌘

New page

{{Cat|OCEB B200.3 - BPMN|01}}
{{Cat|OCEB T200.2 - BPMN|01}}
{{OCEB Links}}

<slideshow style="nobleprog" headingmark="⌘" incmark="…" scaled="false" font="Trebuchet MS" >
;title: BPMN v1.1 - Element Attributes
;author: Bernard Szlachta (NobleProg Ltd)
</slideshow>

== Common Process Attributes ⌘==
; ProcessType : String
: '''None''' | Private | Abstract | Collaboration

; Status : String
: '''None''' | Ready | Active | Cancelled | Aborting | Aborted | Completing | Completed

; GraphicalElements (0-n) : Object
: all the objects contained within the Business Process (Events, Activities, Gateways, Artifacts, etc..)

; Performers (0-n) : String
: defines the resource that will be responsible for the Process.
: specific individual, a group, an organization role or position, or an organization.

; Assignments (0-n) : Assignment
: The Assignment SHALL be performed as defined by the AssignTime attribute. (more details later)

; Properties (0-n) : Property
* Modeler-defined Properties MAY be added to a Process
* These Properties are ''local'' to the Process
* All embedded elements SHALL have access to these Properties
* Full name: <process name>.<property name> (e.g. Order.WikiLink)

; InputSets (0-n) : InputSet
* defines the data requirements for input to the Process
* Zero or more InputSets MAY be defined
* Each Input set is sufficient to allow the Process to be performed (if it has first been instantiated by the appropriate signal arriving from an incoming Sequence Flow)
* (more details later)

; OutputSets (0-n) : OutputSet
* defines the data requirements for output from the Process
* Zero or more OutputSets MAY be defined
* At the completion of the Process, only one of the OutputSets may be produced
* It is up to the implementation of the Process to determine which set will be produced
* However, the IORules (see outputSetRefs in BPMN 2.0) attribute MAY indicate a relationship between an OutputSet and an InputSet that started the Process
* ( more details later)

== Common Activity Attributes ⌘==
;Status
: String
: ('''None''' | Ready | Active | Cancelled | Aborting | Aborted | Completing | Completed)
* determined when the activity is being executed by a process engine
* can be used within Assignment Expressions

; Performers (0-n) : String
* defines the resource that will perform or will be responsible for the activity
* could be in the form of a specific individual, a group, an organization role or position, or an organization

; Properties (0-n) : Property
* Modeler-defined Properties MAY be added to an activity
* ''local'' to the activity
* These Properties are only for use within the processing of the activity
* The fully delineated name of these properties is “<processname>.<activity name>.

; InputSets (0-n) : InputSet
* defines the data requirements for input to the activity.
* Zero or more InputSets MAY be defined
* Each InputSet is sufficient to allow the activity to be performed (if it has first been instantiated by the appropriate signal arriving from an incoming Sequence Flow)

; OutputSets (0-n) : OutputSet
* defines the data requirements for output from the activity
* At the completion of the activity, only one of the OutputSets may be produced
* It is up to the implementation of the activity to determine which set will be produced. * IORules attribute MAY indicate a relationship between an OutputSet and an
InputSet that started the activity

; IORules (0-n) : Expression
* The IORules attribute is a collection of expressions, each of which specifies the
required relationship between one input and one output
* That is, if the activity is instantiated with a specified input, that activity shall complete with the specified output.

; StartQuantity 1 : Integer
* The default value is 1.
* The value MUST NOT be less than 1
* defines the number of Tokens that must arrive before the activity can begin.

; CompletionQuantity 1 : Integer
* The value MUST NOT be less than 1
* defines the number of Tokens that must be generated from the activity
* This number of Tokens will be sent done any outgoing Sequence Flow (assuming any
Sequence Flow Conditions are satisfied).

; LoopType : String
: ('''None''' | Standard | MultiInstance)
* A Task of type Receive that has its Instantiate attribute set to True MUST NOT have a Standard or MultiInstance LoopType.

== Assignment ==
;To : Property The target for the Assignment MUST be a Property of the Process or the activity
itself.
;From : Expression The Expression MUST be made up of a combination of Values, Properties, and
Attributes, which are separated by operators such as add or multiply. The expression
language is defined in the ExpressionLanguage attribute of the Business Process
Diagram - see “Business Process Diagram Attributes on page 241.”
AssignTime (0-1) (Start | End)
;Start : String
An Assignment MAY have a AssignTime setting. If the Object is an activity (Task,
Sub-Process, or Process), then the Assignment MUST have an AssignTime.
A value of Start means that the assignment SHALL occur at the start of the activity.
This can be used to assign the higher-level (global) Properties of the Process to the
(local) Properties of the activity as an input to the activity.
A value of End means that the assignment SHALL occur at the end of the activity.
This can be used to assign the (local) Properties of the activity to the higher-level
(global) Properties of the Process as an output to the activity.

== AdHoc process attributes ⌘ ==
; AdHoc False : Boolean
* the activities within an Ad Hoc Process are not
controlled or sequenced in a particular order
* their performance is determined by the performers of the activities

; AdHocOrdering (0-1) : String
: Sequential | '''Parallel'''
* Sequential is a restriction on the performance that may be required due to shared resources

; AdHocCompletionCondition(0-1) : Expression
* If the Process is Ad Hoc (the AdHoc attribute is True), then the AdHocCompletionCondition attribute MUST be included
* This attribute defines the conditions when the Process will end

== InputSet ⌘ ==
; ArtifactInputs (0-n) : ArtifactInput
* Zero or more ArtifactInputs MAY be defined for each InputSet.
* For the combination of ArtifactInputs and PropertyInputs, there MUST be at least one item defined for the InputSet
* An ArtifactInput is an Artifact, usually a Data
Object
* Note that the Artifacts MAY also be displayed on the diagram and MAY be connected to the activity through an Association (not required)

=== ArtifactInput ⌘ ===
; ArtifactRef : Artifact
* identifies an Artifact that will be used as an input to an activity
* the Artifact will be part of an InputSet for an activity

; RequiredForStart : Boolean
: '''True''' | False
* the Input is required for an activity to start
* If False, then the activity MAY start within the input if it is available, but MAY accept the input (more than once) after the activity has started
* An InputSet may have a some of ArtifactInputs that have this attribute set to True and some that are set to False.

== OutputSet ⌘ ==
; ArtifactOutputs (0-n) : ArtifactOutput
* For the combination of ArtifactOutputs and PropertyOutputs, there MUST be at least one item defined for the OutputSet
* An ArtifactOutput is an Artifact, usually a Data
Object
* Artifacts MAY also be displayed on the diagram and MAY
be connected to the activity through an Association　（not required）

；PropertyOutputs (0-n) : Property
* For the combination of ArtifactOutputs and PropertyOutputs, there MUST be at least one
item defined for the OutputSet

=== ArtifactOutput ⌘ ===
; ArtifactRef : Artifact
* identifies an Artifact that will be used as an output from an activity.
* identified Artifact will be part of an OutputSet for an activity

; ProduceAtCompletion : Boolean
* The default True
* This means that the Output will be produced when an activity has been completed
* If False, then the activity MAY produce the output (more than once) before it has completed.
* An OutputSet may have a some of ArtifactOutputs that have this attribute set to True and some that are set to False

BPMN v1.1 - Element Attributes - Revision history

Bernard Szlachta: /* Common Activity Attributes ⌘ */