Continuation in Long-Running Calls

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.

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

For Flexcards that call long-running Integration Procedures that have an HTTP Action or a Remote Action, enable continuation support by adding a new Options Map to the Integration Procedure data source. Enter useContinuation as the key and true as the value.

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 — This approach is older, still supported but deprecated.

• Make a Long-Running Remote Call Using Omnistudio.OmniContinuation — This approach is recommended because it's namespace-independent.

• Make a Long-Running Remote Call Using VlocityContinuationIntegration
  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
  To support long-running remote calls, Vlocity supports the use of the Salesforce Continuation object.