Omnistudio Fundamentals18% of the exam
Testing, versioning and cloning Omnistudio components
How to test each Omnistudio component with its designer's Preview, test parameters and test data, Apex unit tests and Test Procedures for Integration Procedures, and UTAM for end-to-end UI tests, plus the versioning and cloning rules for Flexcards, Omniscripts, Integration Procedures and Data Mappers.
Explain testing, versioning, cloning where applicable through Omnistudio components.
~8 min read · 10 practice questions ·
What the exam expects
- Test each component in its designer's Preview with test parameters, input and test data, knowing what each Preview can't do or does for real.
- Unit test Integration Procedures from Apex on the core runtime and with Test Procedures on the Managed Package Runtime, including what must be mocked.
- Choose UTAM for durable end-to-end UI tests.
- Apply versioning and cloning rules for Flexcards, Omniscripts, Integration Procedures and Data Mappers, including Data Mapper Versioning and Clean Metadata version behaviour.
Key terms:
- Preview: the designer tab that runs a component with test input and shows its data JSON and action debugger.
- Test Procedure: an Integration Procedure that unit tests another component; its transaction rolls back.
- UTAM: UI Test Automation Model, a Page Object framework for Omnistudio UI tests.
- Version: a copy of a component under the same name, of which only one is active.
Key facts
Flexcard Preview
- Detail
- Navigate and Omniscript actions don't work
Data Mapper Preview
- Detail
- Load results are saved permanently
Apex IP tests
- Detail
- seeAllData on @isTest; no HTTP mocking in core runtime
Test Procedures
- Detail
- Run in IDX Workbench; transaction rolled back
Must mock
- Detail
- Docusign Envelope, Email and HTTP Actions
Flexcard versions
- Detail
- One active at a time; activating one deactivates the others
IP versions
- Detail
- A new version doesn't affect the calling tool
Data Mapper Versioning
- Detail
- Per the Versioning page: existing become version 1; can't be disabled; "No active version" error. The Best Practices page differs after 242.8
Sources for this section (8)
- Preview and Debug a Flexcardhelp.salesforce.com (opens in a new tab)
- Preview and Test Data Mappershelp.salesforce.com (opens in a new tab)
- IP Unit Testing from Apexhelp.salesforce.com (opens in a new tab)
- Test Procedureshelp.salesforce.com (opens in a new tab)
- Clone or Create a New Versionhelp.salesforce.com (opens in a new tab)
- Configure Your Integration Proceduretrailhead.salesforce.com (opens in a new tab)
- Best Practiceshelp.salesforce.com (opens in a new tab)
- Data Mapper Versioninghelp.salesforce.com (opens in a new tab)
- Why does an Apex unit test of an Integration Procedure need seeAllData=true?
- When does a Test Procedure require you to mock an action?
- Which Flexcard option creates a separate card with the same layout instead of a new version?
- Why should you create a new version before opening an activated component in the standard designer?
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 (10 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams