Integration Procedure Actions (Managed Package)

For the managed package runtime, to compose an Integration Procedure, you add actions that run sequentially. These actions can set data values, perform functions, call Omnistudio Data Mappers, invoke Apex classes, send emails, invoke REST endpoints, run other Integration Procedures, and more.

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

To add an action, drag it from the palette into the Structure panel, then configure its properties. You can edit, rename, move, and delete actions. You can also use blocks to group actions for conditional execution, caching, list processing, and error handling.

For details about specific Integration Procedure actions, see the topics for the actions.

• Common Integration Procedure Action Properties (Managed Package)
  For the managed package runtime, to compose an Integration Procedure, you add a sequence of actions. To configure an action, you set the action's properties. Standard properties that exist in most or all actions are listed here. All properties are of the String data type unless otherwise noted.
• Set Values for Integration Procedures (Managed Package)
  For the managed package runtime, the Set Values action sets values in the data JSON of an Integration Procedure literally, using merge fields, or using formulas. This action has many uses. The example includes the most common uses.
• Assert Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Assert Action compares the expected and actual results of a Test Procedure using an expression that evaluates to true or false. You can use environment variables in the Assert Conditional Formula to test performance.
• Batch Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Batch Action runs a Vlocity Scheduled Job with a Data Source Type of Data Input, Query, List Input, or No Input. A Vlocity scheduled job calls either another Integration Procedure or a VlocityOpenInterface.
• Calculation Action for Integration Procedures (Managed Package)
  For the managed package runtime, a Calculation Action invokes the specified calculation procedure and returns the results to the Integration Procedure.
• Chatter Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Chatter Action creates a Chatter post and sends it to a Chatter feed.
• Omnistudio Data Mapper Extract Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Data Mapper Extract Action calls the specified Data Mapper Extract to read data from Salesforce and returns it to the Integration Procedure.
• Omnistudio Data Mapper Post Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Data Mapper Post Action calls a Data Mapper Load (post) to write data to Salesforce.
• Omnistudio Data Mapper Transform Action for Integration Procedures (Managed Package)
  For the managed package runtime, a Data Mapper Transform Action calls the specified Data Mapper Transform to execute transformations on the Data JSON and returns the transformed data.
• Omnistudio Data Mapper Turbo Action for Integration Procedures (Managed Package)
  For the managed package runtime, a Data Mapper Turbo Action calls the specified Data Mapper Turbo Extract to read data from Salesforce and returns it to the Integration Procedure.
• DocuSign Envelope Action for Integration Procedures (Managed Package)
  For the managed package runtime, the DocuSign Envelope Action emails a set of documents for signing.
• Email Action for Integration Procedures (Managed Package)
  For the managed package runtime, an Email Action sends the specified email. You can either specify all the email field values or use a Salesforce email template.
• HTTP Action for Integration Procedures (Managed Package)
  For the managed package runtime, the HTTP Action executes a REST call and returns its results to the Integration Procedure.
• Integration Procedure Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Integration Procedure Action runs a subordinate Integration Procedure.
• Intelligence Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Intelligence Action provides input to and runs a Vlocity Intelligence Machine.
• List Merge Action for Integration Procedures (Managed Package)
  For the managed package runtime, the List Merge Action merges multiple lists by matching values of specified list item JSON nodes. A basic merge matches node names exactly. An advanced merge matches nodes that have different names and/or reside at different levels in the incoming lists.
• Matrix Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Matrix Action calls a calculation matrix with specified inputs and returns the result to the Integration Procedure.
• OmniForm Action for Integration Procedures (Managed Package)
  For the managed package runtime, the OmniForm Action launches the specified OmniForm.
• Remote Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Remote Action element calls the specified Apex class and method or the specified invocable action. You can also pass in invocation options and data. The Apex class must implement the VlocityOpenInterface2 or Callable interface.
• Response Action for Integration Procedures (Managed Package)
  For the managed package runtime, the Response Action ends an Integration Procedure and returns data to the entity that called it. It can also add data to the data JSON or end conditionally. Response Actions are useful for debugging Integration Procedures.