An operation is contained by a service interface, and which comprises input and output elements defined in terms of messages or message parts.
An operation can be created in the following diagrams with any orchestration languages:
-
Choreography Diagram
-
Process Service Diagram
An operation belongs to a service interface which, in turn, belongs to a service provider (see Service Providers (BPM)). The operation describes the implementation of an atomic process, and can be sent or received by an activity (see Example: Using the Execute Operation Implementation Type).
The Dependencies tab of the operation property sheet allows you to visualize all the processes implemented by the current operation. Shortcuts for operations are not permitted.
If you copy an operation within the same model, the associated messages are reused, and if you copy it to another model, the messages are also duplicated. If you move:
- An operation to another service interface in the same model - All the links to the processes that use the operation are deleted. However, if you move an operation to another service provider all operation messages are duplicated.
- An operation from the browser to a process in the diagram window - The process is implemented by the operation (see Example: Using the Execute Operation Implementation Type).
- A service provider to another model - Its service interfaces and operations are also moved. 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.