Convert a Basic Routing Integration to an App Driven Orchestration Integration

You must convert basic routing integrations to app driven orchestration integrations. Basic routing integrations offer limited action capabilities and are being deprecated. App driven orchestration integrations provide greater flexibility with more action capabilities.

Note:

Basic routing scheduled integrations, publish to OIC integrations, subscribe to OIC integrations, and asynchronous integrations with a delayed response cannot currently be converted.

1. In the left navigation pane, click Home > Integrations > Integrations.
2. Click to filter integrations by style.
3. Go to the row of the basic routing integration to convert. For this example, the following basic routing integration is selected for conversion. Note that routing paths for two different ServiceNow Adapter invoke endpoints have been defined.
   
   
   Description of the illustration convert_basic_routing.png
   
   
4. Select Convert from the menu.

   Note:

   The option is not available for basic routing integrations that are active or locked.
5. In the Select Conversion Option section, select the type of conversion to perform.
   • Copy as New App Driven Orchestration Integration: Creates a new app driven orchestration integration copy from the basic routing integration. This enables both integration styles to exist together until you are ready to delete the basic routing integration style.
   • Overwrites the selected Basic Routing Integration: Overwrites the existing basic routing integration with a new app driven orchestrated integration.
6. Optionally enter a new name for the integration that can always be changed later.
7. Accept the default values or enter new values for the identifier and version. These cannot be changed later. Their combination must be unique.
   
   
   Description of the illustration convert_integration.png
   
   
8. Click Convert.

   When conversion completes, the following message is displayed:

   CONFIRMATION
   Integration Integration_Name (version_number) was converted successfully. 

9. Open the converted integration. Note that the routing path in the basic routing integration was converted to a switch action that includes the two different ServiceNow Adapter invoke endpoints.
   
   
   Description of the illustration converted_app_driven.png
   
   
10. Activate the integration. See Activate an Integration.

Faulted Integrations Behavior After Conversion

There is a change in behavior for faulted integrations after basic routing to app driven orchestration integration conversion is complete. When a synchronous basic routing integration fails, a failed tracking instance is created. The failed integration is visible on the Tracking Details page for that integration under Home > Monitoring > Integrations.

Description of the illustration convert_routing_fault.png

If you select View Errors from the menu, the following error is displayed.

Error while invoking target service "integration_name" for sync flow. 
The Error was raised back to the calling client.

After conversion to an app driven orchestration integration, the tracking instance is marked as succeeded for this integration. This is because the failure is handled in a scope fault handler.

If you select View Activity Stream from the menu, the following message is displayed.

Error Message is - Error has been recovered. No message to display.

Therefore, the integration is marked as succeeded instead of failed.