Omniscript step flow, conditional views and languages
How to branch one Omniscript with Steps and conditional views (Show Element if True, Disable Read Only if True, Set Element to Required if True, AND/OR groups), why hidden elements become null, and how one multi-language Omniscript serves several languages through custom labels.
Recommend effective multi-step, conditional, and branched Omniscript designs that align with defined business processes and user journeys, including multi-language support.
~7 min read · 9 practice questions ·
What the exam expects
- Recommend one branched Omniscript instead of copies: Steps for pages, conditional views to show or skip Steps and Blocks.
- Pick the conditional view type from the requirement (hide, keep read-only until, make required when) and combine conditions with AND or OR.
- Predict what happens to data the user can no longer see, and design later checks around it.
- Plan a multi-language Omniscript: prerequisites, custom labels, translated Select options and how the launch URL picks the language.
Key terms: Step (one page of the journey); Block (groups elements into nested JSON inside a Step); conditional view (a condition on a Step, Block or element that controls visibility, read-only or required state); data JSON (the Omniscript's running data); multi-language Omniscript (one Omniscript whose text comes from translated custom labels).
Key facts
- Detail
- Show Element if True, Disable Read Only if True, Set Element to Required if True
- Detail
- Show Element if True is the only condition type
- Detail
- Not supported; adding it in the JSON editor doesn't work
- Detail
- Set to null in the data JSON
- Detail
- Blocked while a required field is empty or a field fails validation
- Detail
- Translation Workbench enabled
- Detail
- Multi-Language value on the Omni Process Language picklist, then selected on the Omniscript
- Detail
- English first; Set Values and Set Errors don't support custom labels
- Detail
- Language code URL parameter, such as c__LanguageCode=es
Sources for this section (6)
- Conditional Viewhelp.salesforce.com (opens in a new tab)
- Stepshelp.salesforce.com (opens in a new tab)
- Multi-Language Omniscriptshelp.salesforce.com (opens in a new tab)
- Enable Multi-Languagehelp.salesforce.com (opens in a new tab)
- Custom Labelshelp.salesforce.com (opens in a new tab)
- Launch Multi-Languagehelp.salesforce.com (opens in a new tab)
- Why does a later completeness check fire for users who never saw a conditional field?
- When should a conditional view use OR instead of AND?
- Which condition type keeps a visible field locked until a checkbox is ticked?
- Why enter English (US) custom label values before other languages?
- What decides the language a multi-language Omniscript renders in when launched from a link?
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 (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams