Continuation in Long-Running Calls (Managed Package)

For the managed package runtime, to support long-running calls, Salesforce provides Apex Continuations. If your Omniscript calls a long-running Integration Procedure or Apex class, you can enable continuation. If your Flexcard calls a long-running Integration Procedure that has an HTTP action or a Remote Action, you can enable continuation.

This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

Note Beginning Winter ‘23, Flexcards supports long-running calls from an Integration Procedure that have an HTTP Action or a Remote Action.

For Omniscripts that call long-running Integration Procedures, check the Use Continuation setting in the Integration Procedure Action.

For Omniscripts that call Apex classes using Remote Actions, you have two options:

• Make a Long-Running Remote Call Using VlocityContinuationIntegration (Managed Package) — This approach is older, still supported but deprecated.

• Make a Long-Running Remote Call Using Omnistudio.OmniContinuation (Managed Package) — This approach, available in Summer '21 or later, is recommended because it's namespace-independent.

• Make a Long-Running Remote Call Using VlocityContinuationIntegration (Managed Package)
  For the managed package runtime, to support long-running remote calls, Vlocity supports the use of the Salesforce Continuation object. The VlocityOpenInterface2 interface and VlocityContinuationIntegration class support normal Remote Calls and Remote Calls that use the Continuation Object. For the new Apex classes, don’t use VlocityOpenInterface.
• Make a Long-Running Remote Call Using Omnistudio.OmniContinuation (Managed Package)
  For the managed package runtime, to support long-running remote calls, Vlocity supports the use of the Salesforce Continuation object.