Explore Integration Procedure Designer Elements
Learning Objectives
After completing this unit, you’ll be able to:
- Add Integration Procedure elements to the canvas.
- List the three categories of Integration Procedure elements.
- Describe the elements across Groups, Data Mapper Actions, and Standard Actions.
Combine Elements to Build Your Integration Procedure
The Integration Procedure Designer provides a variety of elements that you can drag onto the canvas to build your server-side processes and data integrations. To add elements to the canvas, drag one from the Elements panel onto the canvas. You can also click 
in the canvas and select an element. All the elements that you add to the Integration Procedure Designer canvas run sequentially from top to bottom.
Integration Procedure elements are divided into Groups, Data Mapper Actions, and Standard Actions. Let’s find out more about them.
Groups
In an Omnistudio Integration Procedure, you run a group of related steps as a unit inside a block to execute them conditionally. You can also cache them, repeat them for each item in a list, or return an error if they fail.
Integration Procedures provide these group types.
Group Type |
What It Does |
Example |
|---|---|---|
Cache Block |
|
An Integration Procedure caches weekly sales numbers but doesn't cache quickly changing stock prices. |
Conditional Block |
|
Based on a price and a state code, an Integration Procedure calculates the sales tax and reports the total price. |
Loop Block |
|
A user adds four products to a digital shopping cart. One Remote Action within a Loop Block adds all the products. Without a Loop Block, adding four products to a cart requires running four separate Remote Actions. |
Try-Catch Block |
|
An Integration Procedure creates and deletes a Contact with a specified LastName and returns an error message if the LastName field is blank. |
You can nest blocks within other blocks. For example, you can nest a Loop Block within a Try Catch Block or a Cache Block.
All groups have one property in common—an Execution Conditional Formula. If this formula evaluates to true or isn't defined, the block is executed. If it evaluates to false, the block is skipped.
Data Mapper and Standard Actions
Action elements are essential building blocks of every Integration Procedure. Actions set data values, perform functions, call Omnistudio Data Mappers, invoke Apex classes, send emails, invoke REST endpoints, run other Integration Procedures, and more. You choose the action that matches the data source you plan to use.
There are two types of actions in the Integration Procedure Designer: Data Mapper Actions and Standard Actions.
- Use Data Mapper Actions to extract, load, and transform Salesforce data with an Omnistudio Data Mapper. Check out Omnistudio Data Mappers in Salesforce Help to learn more about them.
- Use Standard Actions to perform routine operations: set data values, invoke Apex classes, send emails, invoke REST endpoints, run other Integration Procedures, and more.
You can also use groups to combine actions for conditional execution, caching, list processing, and error handling. Take a look at the various types of Standard Action elements.
Action Type |
What It Does |
|---|---|
Assert |
Compares the expected and actual results of a test procedure using an expression that evaluates to true or false. Use environment variables in the Assert Conditional Formula to test performance. |
Chatter |
Creates a Chatter post and sends it to a Chatter feed. |
Decision Matrix |
Calls a Decision Matrix with specified inputs and returns the result to the Integration Procedure. Check out Decision Matrices for more details. |
Delete |
Deletes one or more object records. Use an object's Record Id to determine which record to delete. |
Docusign Envelope |
Emails a set of documents for signing. |
Sends an email. Specify all the email field values or use a Salesforce email template. |
|
Expression Set |
Invokes an Expression Set and returns the results to the Integration Procedure. |
HTTP |
Executes a REST call and returns its results to the Integration Procedure. |
Integration Procedure |
Runs a child Integration Procedure. Parent and child Integration Procedures transform a list of paired values into a list of keys and values. |
List |
Merges multiple lists by matching the values of specified list item JSON nodes. A basic merge matches node names exactly. An advanced merge matches nodes that have different names or reside at different levels in the incoming lists. |
Remote |
Calls the specified Apex class and method, or the specified invocable action. You can also add invocation options and data. The Apex class must implement the Callable interface. |
Response |
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. |
Set Values |
Sets values in the data JSON of an Integration Procedure, using merge fields or formulas. Defines, assigns, or manipulates data within the Integration Procedure's data JSON. |
Each element gives you options to configure, duplicate, and delete it. So how do you configure an element after adding it to the canvas?
To configure an element, click 
and select Details from the dropdown. A panel appears on the interface where you can configure the details of the element.
What’s Next
In this unit, you learned about the various elements you can use to build Integration Procedures.
In the next unit, explore how to configure Integration Procedures using the properties panel. Also, learn about the send and response transformations feature and best practices to follow before using Integration Procedures.