Omnistudio Fundamentals16% of the exam
Scoping requirements, assumptions, risks and constraints
How a consultant turns discovery notes into an Omnistudio design: sorting statements into requirements, assumptions, risks and constraints, mapping each requirement to a component, flagging governor-limit and runtime constraints early, and outlining the plan end to end.
Determine a projects needs by evaluating a customer's requirements, assumptions, risks, and constraints.
~8 min read · 10 practice questions ·
What the exam expects
- Sort a discovery statement into a requirement, an assumption, a risk or a constraint, and say what to do with each.
- Map each requirement to the Omnistudio component that meets it, and spot requirements no standard capability supports.
- Challenge assumptions that a declarative design escapes governor limits or performance testing.
- Surface runtime and designer constraints at discovery (Streaming API data sources, SLDS 2 theme, Omni Analytics, OmniOut).
- Turn the design into an implementation plan that outlines the whole process before building.
- Key terms: requirement (what the solution must do); assumption (something the plan treats as true without proof); risk (an uncertain event that could hurt the project); constraint (a fixed limit the design must work within). These four definitions are the exam's working vocabulary (Exam convention); no Salesforce page defines them.
Key facts
Integration Procedure fit
- Detail
- No user interaction during execution; one server call; can cache
Too many data calls in one IP
- Detail
- Risks SOQL limit errors; keep a small group of related functions per IP
Async IP from an Omniscript
- Detail
- Continues on Next; stops if the user navigates away from the Omniscript
Omniscript size
- Detail
- Try to limit a single Omniscript to a maximum of 750 elements
Governor limits
- Detail
- Apply to Omnistudio; debug logs capture usage for Omniscripts, IPs and Data Mappers
Streaming API data source
- Detail
- Only with the designer on a managed package
Analytics on Standard Runtime
- Detail
- Omni Analytics works with Google Analytics 4; no Tracking Service
SLDS 2
- Detail
- Omnistudio SLDS 2 theme aligns with the org's SLDS and SLDS 2 theme
Turbo Extract
- Detail
- No formulas, custom JSON, default values or transformations
Sources for this section (7)
- Omnistudio Integration Procedureshelp.salesforce.com (opens in a new tab)
- Integration Procedure Best Practiceshelp.salesforce.com (opens in a new tab)
- Omniscript Best Practiceshelp.salesforce.com (opens in a new tab)
- Set Up a Data Source on a Flexcardhelp.salesforce.com (opens in a new tab)
- Supported Featureshelp.salesforce.com (opens in a new tab)
- Omnistudio Settingshelp.salesforce.com (opens in a new tab)
- Omnistudio Data Mappershelp.salesforce.com (opens in a new tab)
- Why is "the async Integration Procedure always finishes" a risk rather than a safe assumption?
- When should a requirement map to an Integration Procedure?
- What element count should a single Omniscript stay within?
- Why is one Integration Procedure for an entire application a risk?
- Which analytics option should a Standard Runtime design name for Google Analytics 4?
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