WPS: Business Process Elements: Activities

Activities are the individual business tasks that implement the larger business goal represented by the process.
An activity can be divided as basic, structured, or associated with processing.

Basic Activities : The basic activity implements a singular aspect or task with in a business process. Basic activities are do not embed other activities within them.

List Of Basic Activities :

 

Invoke activity :  

 

Use this activity to call an operation on a specific partner. Operations can be either one-way (asynchronous) or request/response (synchronous). 

Assign activity : 







Use this activity for basic data manipulation through the use of expressions, to map service endpoint references to or from partner links, or to copy some form of information from one part of your process to another.

Receive activity :  

 

The receive activity provides Web services to the process partners by waiting for external input from the partners, and channeling it into the process. It can have one or more associated reply activities if it is used in request-response operations.

Receive activities can either start a process, or receive a message in an already running process. Configure the receive activity to be one of these types using the Create a new process instance if one does not already exist setting on the Details tab of the Properties view. When selected the receive activity starts a new process.

Receive choice activity :  

 

It is a combination of receive and choice. When a specific message is received, a matching path of activities are executed.

• Receive choice can be used to start a process instance. 
• This activity waits for 1 to N possible messages. 
• A correlation set specified for each case. 
• Each case can have different permissions. 
• If we select an interface with multiple operations when a process is created, it begins with a receive choice instead of receive.
• A timeout case executes control path if a message is not received with in a certain time evaluated by an expression. Timeout is an IBM extension to BPEL 

 Selects one branch of activities to execute based on receive case. Receive cases are interface operations  

Reply activity :  

 

Use this activity in a synchronous (request/response) operation to return the output or fault to the partner that initiated the operation. This activity specifies the same partner implementation as the corresponding receive activity. A reply is always sent to the same partner from which a message was previously received.

Wait activity :  

 

Use this to stop the process for a specified period of time. You configure this activity either by telling it how long it should hold up the process, or by specifying when it has waited long enough. 

Empty action activity :  

 

Use this activity as an undefined object to act as a placeholder within your process. You might do this if you were designing a process that you expected somebody else to implement, or if you were trying to synchronize the activities within a parallel activity.  

Snippet activity :  

 

Use this activity to compose visual expressions and Java™ code and thereby insert custom behavior into your process. 

Business Object Map activity :  

 Use this activity to compose a mapping between process variables that refer to business objects. Variables that do not point to business objects cannot be transformed using a business object map.

Note: You must create a new business object map each time you want to use one. Reuse of business object maps is not supported.