Mapping heritage service artifacts to service flow artifacts

Learn about the artifacts that are created when you convert a heritage service that was built in the desktop Process Designer so that you can use it in the Process Designer.

Converting a heritage service creates an equivalent service flow in the Process Designer. By using the Service Flow editor in the Process Designer, you can add other services, events, and gateways to your service flow. During conversion, artifacts in the heritage service are replaced with their equivalent in the Service Flow editor. Artifacts that do not have a direct equivalent in the Process Designer are converted into placeholder Service Task activities.
Important: After conversion, review, test, and edit the service flow in the Process Designer to ensure that all artifacts are present, the logic of the initial service is implemented correctly, and the service flow works as expected. For more information, see Converting heritage services.

Ajax service

In the desktop Process Designer, you use an Ajax service when you want a coach view to send data to or retrieve data from the server asynchronously, such as for auto-completion in text fields, for default selection values in selection lists, and so forth. When you convert an Ajax service, a corresponding service flow is created, with an equivalent artifact for each component.

The following table shows the mapping between the Ajax services in the desktop Process Designer and their equivalent service flow artifacts in the Process Designer after conversion.

Table 1. Mapping of Ajax service artifacts
Ajax service Service flow
This screen capture shows the Content Integration component
Content Integration		 This icon indicates the Content Integration tool on the palette. Content Task activity
This screen capture shows the Server Script component. Server Script This icon indicates the Script tool on the palette. Server Script task
This screen capture shows the Server Scriptlet component. Server Scriptlet This icon indicates the Script tool on the palette. Server Script task
This screen capture shows the Modify Task component. Modify Task This icon indicates the Modify Task tool on the palette. Modify Task activity
This screen capture shows the Decision Gateway component. Decision Gateway This icon indicates the Exclusive Gateway tool on the palette. Exclusive gateway
This screen capture shows the End Event component. End Event This icon indicates the None end event tool on the palette. End event
This screen capture shows the Note component. Note This icon indicates the Note tool on the palette. Note
This screen capture shows the Error End Event component. Error End Event
Note: For information on how to handle error events from releases earlier than V8.0, see Error events in models from V7.5.x and earlier.
 This icon indicates the Error end event tool on the palette. Error end event
This screen capture shows the Invoke UCA component. Invoke UCA This icon indicates the Message (sending) tool on the palette. Intermediate message (sending) event
This screen capture shows the Error Intermediate Event component. Error Intermediate Event This icon indicates the Error tool on the Service Flow palette. Intermediate error event
This screen capture shows the Intermediate Tracking Event component. Intermediate Tracking Event This icon indicates the Tracking event tool on the palette. Intermediate tracking event
This screen capture shows the Nested Service component. Nested Service This icon indicates the Linked Service Flow tool on the palette. Linked Service Flow activity
This screen capture shows the Send Alert component. Send Alert This icon indicates the Service Task tool on the palette. Service Task activity
Restriction: The Send Alert artifact is converted into a placeholder Service Task activity. No equivalent in the Process Designer is available.

Integration service

In the desktop Process Designer, you use an Integration service for outbound integration with web services, Java and ECM content. When you convert an Integration service, an equivalent service flow is created, with a service task for each integration component. For web services and Java integration, external services are created to provide an interface that the service task can call.

The following table shows the mapping between the Integration service artifacts in the desktop Process Designer and their equivalent artifacts in the Process Designer after conversion.

Table 2. Mapping of Integration service artifacts
Integration service Service flow
This screen capture shows the Web Service Integration component. Web Service Integration This icon indicates the Service Task tool on the palette. Service Task activity
An external service is created with a binding to the web service server that contains the configuration information required to access the web service. The external service includes port types and operations that correspond to the WSDL definition of the web service, and the service task is configured to invoke the appropriate external service operation.
Restriction: Web service integration tasks that use the discovery scheme Provide inline configuration are converted to placeholder service tasks. No equivalent function is available in the Process Designer.
See Converting web service integrations.
The screen capture shows the Java integration component. Java Integration This icon indicates the Service Task tool on the palette. Service Task activity

An external service is created that contains operations with inputs and outputs based on the methods in the invoked Java class. The service task is configured to invoke the appropriate operation in the external service.
This screen capture shows the Content Integration component
Content Integration		 This icon indicates the Content Integration tool on the palette. Content task activity
This screen capture shows the Server Script component. Server Script This icon indicates the Script tool on the palette. Server Script task
This screen capture shows the Server Scriptlet component. Server Scriptlet This icon indicates the Script tool on the palette. Server Script task
This screen capture shows the Modify Task component. Modify Task This icon indicates the Modify Task tool on the palette. Modify Task activity
This screen capture shows the Decision Gateway component. Decision Gateway This icon indicates the Exclusive Gateway tool on the palette. Exclusive gateway
This screen capture shows the End Event component. End Event This icon indicates the None end event tool on the palette. End event
This screen capture shows the Note component. Note This icon indicates the Note tool on the palette. Note
This screen capture shows the Error End Event component. Error End Event
Note: For information on how to handle error events from releases earlier than V8.0, see Error events in models from V7.5.x and earlier.
 This icon indicates the Error end event tool on the palette. Error end event
This screen capture shows the Invoke UCA component. Invoke UCA This icon indicates the Message (sending) tool on the palette. Intermediate message (sending) event
This screen capture shows the Error Intermediate Event component. Error Intermediate Event This icon indicates the Error tool on the Service Flow palette. Intermediate error event
This screen capture shows the Intermediate Tracking Event component. Intermediate Tracking Event This icon indicates the Tracking event tool on the palette. Intermediate tracking event
This screen capture shows the Nested Service component. Nested Service This icon indicates the Linked Service Flow tool on the palette. Linked Service Flow activity
This screen capture shows the Send Alert component. Send Alert This icon indicates the Service Task tool on the palette. Service Task activity
Restriction: The Send Alert artifact is converted into a placeholder Service Task activity. No equivalent in the Process Designer is available.

General System service

In the desktop Process Designer, you use a General System service to orchestrate other background services, manipulate variable data, generate HTML for a coach, or perform some other actions that do not require any integrations or business rules. When you convert a General System service, a corresponding service flow is created, with an equivalent artifact for each component.

The following table shows the mapping between the General System services in the desktop Process Designer and their equivalent service flow artifacts in the Process Designer after conversion.

Table 3. Mapping of General System service artifacts
General System service Service flow
This screen capture shows the Server Script component. Server Script This icon indicates the Script tool on the palette. Server Script task
This screen capture shows the Server Scriptlet component. Server Scriptlet This icon indicates the Script tool on the palette. Server Script task
This screen capture shows the Modify Task component. Modify Task This icon indicates the Modify Task tool on the palette. Modify Task activity
This screen capture shows the Decision Gateway component. Decision Gateway This icon indicates the Exclusive Gateway tool on the palette. Exclusive gateway
This screen capture shows the End Event component. End Event This icon indicates the None end event tool on the palette. End event
This screen capture shows the Note component. Note This icon indicates the Note tool on the palette. Note
This screen capture shows the Error End Event component. Error End Event
Note: For information on how to handle error events from releases earlier than V8.0, see Error events in models from V7.5.x and earlier.
 This icon indicates the Error end event tool on the palette. Error end event
This screen capture shows the Invoke UCA component. Invoke UCA This icon indicates the Message (sending) tool on the palette. Intermediate message (sending) event
This screen capture shows the Error Intermediate Event component. Error Intermediate Event This icon indicates the Error tool on the Service Flow palette. Intermediate error event
This screen capture shows the Intermediate Tracking Event component. Intermediate Tracking Event This icon indicates the Tracking event tool on the palette. Intermediate tracking event
This screen capture shows the Nested Service component. Nested Service This icon indicates the Linked Service Flow tool on the palette. Linked Service Flow activity
This screen capture shows the Send Alert component. Send Alert This icon indicates the Service Task tool on the palette. Service Task activity
Restriction: The Send Alert artifact is converted into a placeholder Service Task activity. No equivalent in the Process Designer is available.

Decision service

Decision services use business rules to determine which process implementation is invoked. When you convert a Decision service, a service flow is created with corresponding artifacts. For example, the Decision Table component is converted into a Script activity and a BAL Rule is converted to a Decision Task. However, no equivalent artifacts are available for a JRules Decision Service. Unsupported components are converted into placeholder artifacts. To complete the service, you must implement these placeholder artifacts.

The following table shows the mapping between the Decision service artifacts in the desktop Process Designer and their equivalent artifacts in the Process Designer after conversion.

Table 4. Mapping of Decision service artifacts
Decision service Service flow
This screen capture shows the Decision Table component. Decision Table This icon indicates the Script tool on the Service Flow palette. Server Script Task
This screen capture shows the BAL rule component BAL Rule This screen capture shows the Decision Task activity icon Decision Task activity
This screen capture shows the Operational Decision Manager Decision Service component. JRules Decision Service This icon indicates the Service Task tool on the palette. Service Task activity
Restriction: The IBM® ODM rule artifact is converted into a placeholder Service Task activity. No equivalent in the Process Designer is available. You can use a REST or web service invocation instead. For more information, see Invoking a REST service and Invoking a web service.
This screen capture shows the Server Script component. Server Script This icon indicates the Script tool on the palette. Server Script task
This screen capture shows the Server Scriptlet component. Server Scriptlet This icon indicates the Script tool on the palette. Server Script task
This screen capture shows the Modify Task component. Modify Task This icon indicates the Modify Task tool on the palette. Modify Task activity
This screen capture shows the Decision Gateway component. Decision Gateway This icon indicates the Exclusive Gateway tool on the palette. Exclusive gateway
This screen capture shows the End Event component. End Event This icon indicates the None end event tool on the palette. End event
This screen capture shows the Note component. Note This icon indicates the Note tool on the palette. Note
This screen capture shows the Error End Event component. Error End Event
Note: For information on how to handle error events from releases earlier than V8.0, see Error events in models from V7.5.x and earlier.
 This icon indicates the Error end event tool on the palette. Error end event
This screen capture shows the Invoke UCA component. Invoke UCA This icon indicates the Message (sending) tool on the palette. Intermediate message (sending) event
This screen capture shows the Error Intermediate Event component. Error Intermediate Event This icon indicates the Error tool on the Service Flow palette. Intermediate error event
This screen capture shows the Intermediate Tracking Event component. Intermediate Tracking Event This icon indicates the Tracking event tool on the palette. Intermediate tracking event
This screen capture shows the Nested Service component. Nested Service This icon indicates the Linked Service Flow tool on the palette. Linked Service Flow activity
This screen capture shows the Send Alert component. Send Alert This icon indicates the Service Task tool on the palette. Service Task activity
Restriction: The Send Alert artifact is converted into a placeholder Service Task activity. No equivalent in the Process Designer is available.

Deployment service

In the desktop Process Designer, you use a Deployment service to customize snapshot installation on a workflow server in another environment. When you convert a Deployment service, an equivalent service flow is created, with an equivalent artifact for each component. A deployment service flow is created by default when you create a new process application and is used when you install a snapshot.

For a mapping of Deployment service artifacts in the desktop Process Designer and their equivalent artifacts in the Process Designer after conversion, refer to the Integration service mapping as it is a similar mapping.