Loading
Industries Order Management
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Overview of Industry Order Management Callouts

            You are here:

            1. Salesforce Help
            2. Docs
            3. Industries Order Management

            Overview of Industry Order Management Callouts

            Callouts (also called callout tasks) are orchestration items that allow Order Management to automate integration with external systems during orchestration. There are some out of the box callouts that require less setup than creating your own.

            There are two types of integration to consider before building a callout. Order Management supports both types:

            • Synchronous Integration: The callout expects the external system to complete a given request immediately, and provide a single response. As soon as the callout receives the response, the orchestration workflow continues, and the callout is moved to a Completed state. See: Custom Synchronous Callouts

            • Asynchronous Integration: The callout does not expect an immediate response. Rather, it expects one or more responses at some unknown point in the future. In the meantime, Order Management can't move past this particular task, though it can continue processing unrelated tasks. See: Custom Asynchronous Callouts

            The configuration within the System Interface object determines if the Callout will behave in synchronous or asynchronous mode. More specifically, the Implementation field configured within the System Interface associates the callout to an Apex class that handles the integration. There are a number of out of the box implementations you can use and extend.

            It's important to understand the classes available. You can extend any included class to support different behavior from what is provided in the default implementations.

            Note
            Note

            Along with the two classes noted in the following table, there's a legacy class for synchronous integration: DefaultSystemInterface

            Class

            Description

            Synchronous integration:

            XOMEnhancedSystemInterface

            • In the JSON, includes the hierarchy of the order item or FRL. That is, it notes the parents and children of the item.

            • Can accept DataRaptors to change the default JSON payload.

            • Sends POST requests.

            • Understands conventional HTTP response codes:

              • Success codes: 200, 201, 202, 203, 204, 205, 206, 302, 304

              • Error codes: 408, 426, 500, 502, 503, 504, 440, 444, 520, 522, 523, 524, 525

            • The URL (System SObject) and Path (System Interface SObject) are used to construct the REST endpoint.

            • The URL (System SObject) can also accommodate a named credential (that is, callout:MyNamedCredential/path) but be sure to provide a Path on the System Interface Object. The path cannot be left blank.

            • Automatically completes the orchestration item or task when a response is received.

            Asynchronous integration:

            XOMAsyncSystemInterface

            • Most of the comments for XOMEnhancedSystemInterface apply, except the following:

              • Sends a callback URL as part of the request to the external system, with the expectation that the external system calls back to send a response or interim updates later.

              • The callback URL aligns with the XOMAsyncResponseRESTService endpoint.
            • Custom Asynchronous Callouts
              Configure a callout that waits for a response from a third-party application.
            • Configure a Custom Asynchronous Callout
              You can configure a Callout Task capable of synchronously calling an Integration Procedure, but asynchronously awaiting one or more responses from a third party application.
            • Custom Synchronous Callouts
              Configure a callout task capable of synchronously calling an integration procedure. Synchronous callouts are the easiest to use because they do not require coordination between different components.
             
            Loading
            Salesforce Help | Article