Integration Procedure Invocation (Managed Package)

For the managed package runtime, you can invoke Integration Procedures from other Omnistudio tools such as Omniscripts and Cards. You can also invoke Integration Procedures from Apex classes, batch jobs, REST APIs, or Salesforce flows.

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

• Integration Procedure Invocation from Apex (Managed Package)
  For the managed package runtime, you can invoke an Integration Procedure from Apex code in two ways using the IntegrationProcedureService class in the Vlocity managed package.
• Integration Procedure Unit Testing from Apex (Managed Package)
  For the managed package runtime, you can set up a test class in Apex and use it to call and test an Integration Procedure. You must mock HTTP Action responses.
• Integration Procedure Invocation from REST APIs (Managed Package)
  For the managed package runtime, you can use either a GET or a POST call to invoke an Integration Procedure and retrieve the result. The difference between the two is that a GET call can't include a JSON request body.
• Integration Procedure Invocation from Salesforce Flow (Managed Package)
  For the managed package runtime, to call an Integration Procedure from a Salesforce Flow, create a Salesforce Flow component by defining a class using the Salesforce Developer Console, as shown in the following example. Note that the class must have the @InvocableMethod annotation.
• Batch Jobs for Integration Procedures and Vlocity Open Interfaces (Managed Package)
  For the managed package runtime, the Vlocity batch framework lets you run an Integration Procedure or VlocityOpenInterface on a schedule. Typical use cases are a recurrent billing cycle or a scan for insurance policies that come up for renewal in the next 60 days. When a job is run, it sends its input to an Integration Procedure or Apex method that processes the records.