Integration Procedure actions and sub-procedures
How to configure the common action properties (Send JSON Path and Node, Additional Input, Send Only Additional Input), Set Values, the Data Mapper actions, Remote Actions (reserialize, invocable actions, System.Callable), HTTP Actions, Integration Procedure Actions for sub-procedures and List Actions.
Configure Groups, Data Mapper Actions (Extract, Load, Transform), Standard Actions (Remote Actions, HTTP Actions, Response Actions, Sub-Integration Procedures), etc.
~8 min read · 8 practice questions ·
What the exam expects
- Shape an action's input and output with Send JSON Path, Send JSON Node, Additional Input, Send Only Additional Input and their response counterparts, and predict the JSON they produce.
- Configure Set Values for literals, merge fields, formulas and arrays (Edit as JSON).
- Call Data Mapper Extract, Turbo Extract, Load (Post) and Transform actions from a procedure.
- Configure a Remote Action for an Apex class or an invocable action, and fix output that needs reserializing.
- Configure HTTP Actions, Integration Procedure Actions for sub-procedures, and List Actions that merge lists.
Key terms: Send JSON Path (trims the incoming JSON to one node before the action runs), Send JSON Node (reparents that input under a new name), Additional Input (key-value pairs added to the action's input), Remote Action (calls an Apex class and method or an invocable action), sub-procedure (a child Integration Procedure run by an Integration Procedure Action), Primary List Key (the list whose entries survive a List Action merge).
Key facts
- Detail
{path:{a:b}}becomes{node:{a:b}}
- Detail
- Not supported in Integration Procedures
- Detail
- Action accepts only its Additional Input data
- Detail
- Edit as JSON, then edit
elementValueMap
- Detail
- System.Callable; VlocityOpenInterface is Managed Package only
- Detail
- Remote Option reserialize = true, or RESERIALIZE in a later Set Values
- Detail
- Remote Class DefaultInvocableAction, Remote Method = action name
- Detail
- Only
getBody(); binary needs a Remote Action
- Detail
- Type_Subtype in the Integration Procedure property
- Detail
- Runs as a future method that can return no data
- Detail
- Only that list's entries are retained
Sources for this section (9)
- Send/Responsehelp.salesforce.com (opens in a new tab)
- IP Actionshelp.salesforce.com (opens in a new tab)
- Set Valueshelp.salesforce.com (opens in a new tab)
- Supported Featureshelp.salesforce.com (opens in a new tab)
- Remote Actionhelp.salesforce.com (opens in a new tab)
- Invocable actionhelp.salesforce.com (opens in a new tab)
- HTTP Actionhelp.salesforce.com (opens in a new tab)
- IP Actionhelp.salesforce.com (opens in a new tab)
- List Actionhelp.salesforce.com (opens in a new tab)
- Why must the Apex class behind a Standard Runtime Remote Action use System.Callable rather than VlocityOpenInterface?
- When does a Data Mapper Transform Action skip caching?
- When does a child procedure return no data to its parent?
- What do an HTTP Action's Timeout and Retry Count hold?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 46 lessons of the Omnistudio Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams