Omniscripts17% of the exam

Omniscript design standards and load-time practices

The Omniscript best practices a consultant writes into team standards: reserved ContextId, unique and stable element names, Internal Notes, validating where data is entered, Step design that limits cognitive load, client-side and server-side load-time practices, Design Assistant limits and two documented configuration traps.

Official exam objective
Discuss best practices for Omniscripts.

~6 min read · 8 practice questions ·

What the exam expects

  • Write Omniscript standards for a team: reserved keys, naming, documentation and change rules.
  • Recommend Step layouts that balance cognitive load, with validation on the Step where data is entered.
  • Diagnose slow Omniscripts from the documented client-side and server-side practices, including the 750-element guidance.
  • Use Design Assistant's recommended limits to flag a design before it is built.
  • Recognize two documented configuration traps: duplicated Edit Block rows after resume, and tables in Text Blocks.

Key terms: ContextId (reserved key holding the record Id from the URL); Internal Notes (designer-only documentation on an element); client-side performance (what the browser evaluates and renders); Design Assistant (real-time design alerts against recommended limits); Merge Saved Data JSON (merges a saved session into an updated Omniscript).

Key facts

ContextId
Detail
Reserved key assigned from the URL's record Id; don't assign it
Names
Detail
Unique element and Data Mapper response node names; no renames after production
Element count
Detail
Try to limit a single Omniscript to 750 elements
Nested blocks
Detail
Recursive nested blocks no more than 10
LWC size
Detail
Don't exceed 4 MB; larger shows an inactive or not-deployed error in preview
Element names and load time
Detail
Removing spaces improves load time
Data Mappers per Omniscript
Detail
Recommended limit 5
Edit Blocks per Omniscript
Detail
Recommended limit 10
Text Blocks
Detail
Tables aren't supported
Sources for this section (2)
  • Why shouldn't an Omniscript write a new value into ContextId?
  • When should validations run, according to Omniscript best practices?
  • Why move formulas into Data Mappers when an Omniscript loads slowly?
  • What is Design Assistant's recommended limit for Data Mappers in one Omniscript?

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 (8 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Unlimited timed practice exams

Practice for the Omnistudio Consultant exam