Designer > Implementing a BPMN Task or Event in BPEL > Overview of BPEL Activities

Overview of BPEL Activities

In the default (BPMN) Process Developer editing style, basic activities are organized according to BPMN types: activities and events. In BPEL, there is no distinction: both activities and events are considered activities.
The following table provides brief definitions and links to more details.
Activity Name
Directs a Web service to perform an operation
Manipulates process variables and partner link endpoint references by creating Copy From/To operations for them
An activity that does nothing when it executes. Useful for situations where you need an activity but do not want anything to really happen, for example, suppressing a fault by having the empty be the child of the catch.
Suspends the process. Useful in a catch or catchAll event to catch unexpected errors.
Validates the values of variables against their associated XML and WSDL data definition
(For Process Developer Classic only). For abstract processes. Stands as a placeholder for an activity that would be used in an executable process.
Create a BPEL for People activity. For details, see What is a People Activity? in the Human Tasks section of this help.
Accepts message data from a service partner. Optionally begins a process by creating an instance of the process.
Sends a response to a partner identified in a matching Receive activity
Signals are similar to a throw, differing in that there isn't a fault. A signal throws information that is received by a signal that waits for this information.
Signals a fault. Specifies a standard or custom fault
Passes the fault that was originally caught by the immediately enclosing fault handler to the parent scope
Stops an executable process immediately, resulting in a faulted process.
Stops process execution for a specified amount of time or until a deadline is reached
Compensate Scope
Starts compensation on a specified inner scope that has already completed successfully
Executes the compensation handler on a named scope or executes the default compensation if no scope is named
Breaks out of a scope or a loop in a while or for each activity. Processing continues normally with the next activity.
For BPEL-Centric palette only.) Continues with the next iteration in a loop (while, repeat until, or for each). A convenience activity that simplifies processing without the need of specifying all the conditions that may be required to continue normal processing when a certain condition is met.
Equivalent to the BPEL empty or assign activity, described above.
For information on structured activities, see Different Ways of Structuring Activities.