For the managed package runtime, Integration Procedures and Omniscripts have differences and common features. Some important Integration Procedure features aren't present in Omniscripts.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Unlike Omniscripts, Integration Procedures have no end-user UI, run on the server, and can run either synchronously or asynchronously.
Like Omniscripts, Integration Procedures can call Omnistudio Data Mappers, Integration Procedures, REST endpoints, and Apex methods. Also, like Omniscripts, Integration Procedures can send emails and DocuSign envelopes and manipulate data using functions and variables.
However, Integration Procedures have some useful features that Omniscripts lack:
-
Caching of part or all of the Integration Procedure for performance
-
Unit testing of entities the Integration Procedure calls
-
Chainable and queueable chainable settings for avoiding governor limits
-
Complex list processing and merging
-
Invocation of Integration Procedures from Apex, REST, Flow, and Scheduled Jobs
Blocks specific to Integration Procedures are:
-
Cache Block — Actions within are cached for performance.
-
If-Else Conditional Block — Actions within have mutually exclusive conditions.
-
Loop Block — Actions within run one time for each item in a list.
-
Try-Catch Block — If any action within causes an error, the error is handled, and the Integration Procedure keeps running.
Actions specific to Integration Procedures are:
-
Assert Action — Declares an expected result for unit testing.
-
Batch Action — Runs a Scheduled Job.
-
Chatter Action — Creates a Chatter post.
-
List Action — Merges two lists based on matching key values.
-
Response Action — Returns data to the entity that called the Integration Procedure.