Integration Procedure modularity, caching and long-running settings
Integration Procedure design standards a consultant recommends: small reusable procedures, Conditional Blocks and formulas, Org versus Session caching with Cache Blocks or top-level caching, chainable, queueable, future and continuation options for long-running work, and the Loop Block and encrypted-data checks.
Discuss best practices for Integration Procedures.
~8 min read · 12 practice questions ·
What the exam expects
- Recommend small, reusable Integration Procedures called through the Integration Procedure Action, and the other documented best practices (trim replies, avoid too many data calls, check View Encrypted Data, no empty Loop Blocks).
- Design conditional logic with Execution Conditional Formulas and Conditional Blocks, including Is If Else and a default step.
- Choose Org or Session cache, top-level caching or Cache Blocks, and a time to live within the documented maximums.
- Recommend chainable, queueable, future or continuation options for long-running or fire-and-forget work.
Key terms: Integration Procedure Action (runs a subordinate Integration Procedure); Conditional Block (groups steps behind a formula; Is If Else makes them mutually exclusive); Cache Block (caches the output of the steps inside it); top-level caching (caches the whole procedure's response); chaining (running steps in separate transactions to avoid governor limits).
Key facts
- Detail
- 48 hours (2880 minutes); non-sensitive, shared data only
- Detail
- 8 hours (480 minutes); cleared when the session expires
- Detail
- 5 minutes for both cache types
- Detail
- Its data isn't cached
- Detail
- When parts update data or need different expiry times
- Detail
- An element runs only if both formulas are true
- Detail
- First TRUE element runs; blank last formula is the default
- Detail
- Child runs as a future method and returns no data
- Detail
- Loop Block can't process an array of records
- Detail
- Check View Encrypted Data before showing decrypted values
Sources for this section (7)
- Improve Performance by Using Cachinghelp.salesforce.com (opens in a new tab)
- Cache Blockhelp.salesforce.com (opens in a new tab)
- Cache for Top-Level Integration Procedure Datahelp.salesforce.com (opens in a new tab)
- Define Execution Logichelp.salesforce.com (opens in a new tab)
- Integration Procedure Action for Integration Procedureshelp.salesforce.com (opens in a new tab)
- Work with Data and Listshelp.salesforce.com (opens in a new tab)
- Integration Procedure Best Practiceshelp.salesforce.com (opens in a new tab)
- Why is Session Cache the safer choice for data that belongs to one signed-in user?
- When should a consultant recommend Cache Blocks instead of top-level caching?
- Why might an action inside a Conditional Block not run even though its own formula is true?
- What does Chain On Step do?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 31 lessons of the Omnistudio Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (12 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams