Activities (WS-BPEL 2.0)

Scope activity [composite] - Provides the context which influences the execution behavior of their nested activities, and allow the definition of variables, partner, message exchanges, correlation sets, event handlers, fault handlers, a compensation handler, and a termination handler.

Sequence activity [composite] - Specifies a set of activities that must be executed sequentially in lexical order, and acts as a container for your sequence activities.

Flow activity [composite] - Specifies a set of activities that must be executed concurrently, and acts as a container for your flow activities. A link modeled as a flow with a link stereotype can express synchronization dependencies between activities.

While activity [loop] - Specifies that the nested activities must be repeated until their specified condition becomes true.

ForEach activity [loop] - Executes its scope for a specified count. The execution iterations can occur in parallel or in sequence.

RepeatUntil activity [loop] - Executes the nested activities at least once until the specified condition becomes true.

Wait activity [generate event] - Specifies a delay for a certain period of time or until a certain deadline is reached.

Compensate activity [generate event] - Causes all immediately enclosed scopes to be compensated in default order.

Compensate scope activity [generate event] - Causes one specified child scope to be compensated. To compensate a scope, create a flow from the scope to the compensate activity, and select the generated compensation event in the Events tab of the flow property sheet to use it. When the compensation event is not used by any flow, the scope generating the event is a compensate activity.

Throw activity [generate event] - Specifies a business process which needs to signal an internal fault explicitly.

Rethrow activity [generate event] - Rethrows the fault that was caught by the immediately enclosing <catch> and <catchAll> elements within a <faultHandlers> element.

Receive activity [execute operation] - Specifies that the business process waits for a matching message to arrive. For receive, reply, reply fault, and invoke activities use the Assignments tab to copy the values of message variables or to calculate the value of an expression, and store it in a variable.

Reply activity [execute operation] - Sends a response to a request accepted by a receive activity.

Reply fault activity [execute operation] - Sends a faulted response to a requests accepted by a receive activity.

Invoke activity [execute operation] - Calls a Web service.

Assign activity - update the values of variables with new data. The assign activity should be composed of at least one atomic assign task (see Process Properties).

Validate activity - Validates the values of variables against their associated XML and WSDL data definition. Specify variables (see Variables (BPM)) in the ValidatedVariables tab.

Extension activity - An activity that is not defined by the specification.

Empty activity - An activity that does nothing (for example a fault which needs to be caught and suppressed). Can also provide a synchronization point in a flow activity, and is used to model top-level processes in top-level diagrams (see Top-Level Diagrams (BPEL)).

If activity - Selects one activity to execute from a set of activities. You can also create composite processes with an <<if>> stereotype.

Pick activity - Waits for the occurrence of one event from a set of events, then executes the activity associated with that event.

Exit activity - Immediately ends the business process instance.