Omnistudio and Business Rules Engine in the landscape
Where shared logic belongs (one Integration Procedure reused by Omniscripts, Flexcards, Apex and Flow), how Omnistudio, Flow and Apex call each other, which package-era actions and batch jobs the Standard Runtime lacks, when Document Generation needs Omnistudio, and the benefits and limits of Business Rules Engine tools.
Justify and recommend architectural choices, demonstrating how Omnistudio components fit into the overall Salesforce and enterprise system landscape.
~8 min read · 10 practice questions ·
What the exam expects
- Recommend one Integration Procedure for shared, non-interactive logic that Omniscripts, Flexcards, Apex and Flow reuse.
- Explain how Omnistudio, Flow and Apex call each other instead of copying one rule into several components.
- Spot package-era capabilities the Standard Runtime doesn't have (Intelligence and OmniForm actions, Vlocity scheduled and batch jobs) and redesign around them.
- Use Integration Procedure actions that reach other services (Docusign Envelope, Chatter, Email) instead of rebuilding them.
- Decide whether Salesforce Document Generation needs Omnistudio.
- State the benefits and limits of Business Rules Engine tools, including effective-dated decision matrix versions.
Key terms: Integration Procedure (server-side actions, no user interaction); Remote Action (calls Apex or an invocable action); Business Rules Engine (expression sets plus lookup tables); decision matrix (inputs matched to a row); decision table (lookup over rule records); expression set (stepwise calculation).
Key facts
- Detail
- Omniscript, Flexcard, other procedures, REST API, Flow, Apex method
- Detail
@InvocableMethodclass; Procedure Name as Type_SubType
executeIntegrationProcedure flow action- Detail
- API 64.0+, only for procedures with Agentforce configured
- Detail
- Calls an Apex class and method or an invocable action
- Detail
- Not on Standard Runtime; deprecated in the package
- Detail
- Managed Package Runtime only
- Detail
- Context Service, no extra license; Omnistudio only for Data Mapper mapping
- Detail
- Records in a standard object, custom object or custom metadata type
- Detail
- Start date, end date, rank (ascending); effective date or today
Sources for this section (8)
- Omnistudio Integration Procedureshelp.salesforce.com (opens in a new tab)
- Invocation from Flowhelp.salesforce.com (opens in a new tab)
- Flow for Omnistudiodeveloper.salesforce.com (opens in a new tab)
- Integration Procedure Actionshelp.salesforce.com (opens in a new tab)
- Supported Featureshelp.salesforce.com (opens in a new tab)
- Omnistudio Requirement for Document Generationhelp.salesforce.com (opens in a new tab)
- Business Rules Enginehelp.salesforce.com (opens in a new tab)
- Decision Matriceshelp.salesforce.com (opens in a new tab)
- Why should a Standard Runtime design reuse an existing invocable action through a Remote Action instead of rebuilding its rule in Omniscript formulas?
- When does Salesforce Document Generation need Omnistudio?
- Which permissions do matrix builders and runtime users need?
- When can a Salesforce Flow use a decision table without Omnistudio?
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 (10 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams