ActiveVOS Designer User’s Guide
The BPEL language provides ways to structure and nest activities. ActiveVOS groups the structured activities in the Control Flow (ActiveVOS Classic Container) palette of the Process Editor. Basic activities execute based on rules and conditions set by a parent container.
In addition to using structured containers, you can also structure activities by linking them with the link tool. For more information, see Using Links.
The following table provides brief definitions of control flow activities.
|
Container Name |
Description |
|---|---|
|
(ActiveVOS Classic only). Executes activities in an ordered list |
|
|
(ActiveVOS Classic only). Executes all activities in parallel |
|
|
Executes an activity repeatedly until its condition evaluates to false |
|
|
Executes an activity at least once and repeats until its condition evaluates to true |
|
|
Executes a selected activity based on an incoming message or a time-out event. Includes the Create Instance property to start a process. |
|
|
Executes a selected activity based on branch conditions |
|
|
Provides a context for set of activities, with correlation, compensation, fault handling, event handling, termination handling, and local partner links and variables |
|
|
Iterates over a list of document elements |
|
|
(BPMN only). Equivalent to the BPEL flow activity, described above. |
|
|
(BPMN only). Allows incoming and outgoing links. Equivalent to the BPEL empty activity. |
See also Tips and Tricks - BPMN Design.
Copyright (c) 2004-2010 Active Endpoints, Inc.