Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Activity
A BPMN 2.0 Activity represents work that is performed within a Process. An Activity can be modeled as a:
• | Sub-Process - a compound Activity that is defined as a flow of other BPMN 2.0 elements or |
• | Task - an atomic Activity that cannot be broken down into a smaller unit |
Activities - both Tasks and Sub-Processes - can also, optionally, act as Looping constructs. The OMG BPMN 2.0 Specification defines two types of Looping construct:
• | Standard Loop (while or until) |
• | Multi-Instance Loop (for each) |
BPEL Properties:
• | Double-click on the Activity in the BPEL diagram |
• | Right-click on the Activity | BPEL | BPEL 2.0 Properties |
Reference
Field/Button |
Usage |
See also |
||||||||||||||||||||||||||||
Name |
Specify the name for the Activity.
|
|
||||||||||||||||||||||||||||
Type |
Specify whether the Activity is a:
|
|
||||||||||||||||||||||||||||
Task Type / SubProcess Type |
Depending on the value selected in the Type field, the Task Type / SubProcess Type field has the following values: Task Type :
SubProcess Type :
|
|
||||||||||||||||||||||||||||
Details |
Depending on the selected Task Type, the Details tab changes as follows:
|
|
||||||||||||||||||||||||||||
Select one or more Assignment elements created in the SupportingElements package in this tab (Optional).
|
||||||||||||||||||||||||||||||
Activities can be repeated sequentially, behaving like a loop. Specify the Activity looping details in this tab (Optional).
|
|
|||||||||||||||||||||||||||||
OK |
Save the values entered in the dialog.
|
|
||||||||||||||||||||||||||||
Cancel |
Discard the values entered in the dialog.
|
|
||||||||||||||||||||||||||||
Help |
Display this Help topic.
|
|
||||||||||||||||||||||||||||
General |
Open the UML Properties dialog.
|
Notes
• | The Assignments tab is not applicable for Sub-Process |
• | The Loop Details tab is not applicable for Event Sub-Process |
• | Business Rule, Manual, Script and User Task types cannot be mapped to BPEL 2.0 |
• | Ad-Hoc, Call Activity and Transaction Sub-Process types cannot be mapped to BPEL 2.0 |