ActiveVOS Designer User’s Guide
Basic activities break down into two kinds: those that interact with Web service partners and those that are used internally by the BPEL process.
The following table provides brief definitions and links to more details.
|
Activity Name |
Description |
|---|---|
|
Web service interaction activities |
|
|
Accepts message data from a service partner. Optionally begins a process by creating an instance of the process. |
|
|
Directs a Web service to perform an operation |
|
|
Sends a response to a partner identified in a matching Receive activity |
|
|
People |
Create a BPEL for People activity. For details, see ActiveVOS BPEL for People Online Help |
|
Internal Process Activities |
|
|
Validates the values of variables against their associated XML and WSDL data definition |
|
|
Manipulates process variables and partner link endpoint references by creating Copy From/To operations for them |
|
|
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 |
|
|
Stops process execution for a specified amount of time or until a deadline is reached |
|
|
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. |
|
|
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 loop in a while or for each activity. Processing continues normally with the next activity. |
|
|
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. |
|
|
Suspends the process. Useful in a catch or catchAll event to catch unexpected errors. |
|
|
For abstract processes. Stands as a placeholder for an activity that would be used in an executable process. |
|
For information on structured activities, see Different Ways of Structuring Activities.
Copyright (c) 2004-2008 Active Endpoints, Inc.