Chapter 6 Building an Executable BPM: Working with Service Description Objects

Operations (Executable BPM)

An operation describes the implementation of an atomic process (activity) in the BPM. It can be sent or received by an activity. It is linked to a process using the Implemented by property in the process property sheet.

The Dependencies tab of the operation property sheet allows you to visualize all the processes implemented by the operation.

The operation has no symbol in the diagram, but has the following graphical representation in the Browser:

For more information about atomic processes also called atomic activities, see section Defining processes in an executable BPM in chapter Building an executable BPM: Managing Data and Orchestration.

You create operations under a service interface.

You cannot create shortcuts for an operation.

Copying an operation

When you copy an operation under another service interface within another model you also duplicate all messages (input, output and fault) associated with it.

When you copy an operation under another service interface within the same model associated messages are reused.

Moving an operation

When you move a service provider within another model, you automatically move its service interfaces and operations. If the associated message format and process using the operation are not moved with the service provider, a copy of the whole service provider remains in the initial model to preserve these links.

When you move an operation under another service interface within the same model, it is equivalent to a cut and paste. All the links to processes are lost. However, if you move an operation to another service provider all operation messages are duplicated.

When you drag and drop an operation from the browser to the diagram window, you create an implemented by process. The process is implemented by the operation you dragged and dropped.

For more information about processes implemented by operations, see section Execute operation activity in chapter Building an Executable BPM: Managing Data and Choreography.