The following transformations are executed when you generate an orchestration BPM from an analysis BPM:
Creation of top-level processes - The orchestration BPM requires a top-level process. When a graph of activities is defined under a package or a model, a top-level process is automatically created and the whole graph of activities is moved under it.
For each unrelated set of activities, a top-level process is created. An activity (start, end, process, decision, and synchronization) is related to another one if a flow exists between them or if they are displayed in the same diagram. The diagrams are also moved under the composite process and their contents are preserved.
Merge of multiple start objects - The orchestration BPM does not support multiple start objects in the composite process. All start objects that appear under composite processes and all start objects that appear simultaneously in the same top-level diagram are merged to become one.
Shortcut of process in graphs - A shortcut can be used in an analysis BPM to reuse an existing process. In an orchestration BPM, such a shortcut is replaced with a duplication of the target object, as processes implemented by another process are not supported. For orchestration languages that do not support process reusability, the call of a reusable process is replaced with a duplication of the process. If the reusable process is an unloaded external shortcut, the activity process that calls the shortcut is preserved and detached from the shortcut.
Message format on flows - The orchestration BPM does not support the association of a message format with a flow, as the exchange of information is no longer managed by flows in this type of BPM view. All message formats are automatically detached from flows.
Flow type on flows - In an analysis BPM, a flow can have one of the following flow types: Success, Timeout, Technical Error and Business Error. The Timeout, Technical Error and Business Error flow types are replaced with event objects with Timer or Fault stereotype. Event objects are associated with the flow to define event handlers.
Data - Data objects are automatically replaced with variables. The data attachment to flow or message format is lost.