Omniscripts20% of the exam

Omniscript best practices: limits, performance and naming

The Omniscript recommended limits and Design Assistant alerts, the 4 MB LWC limit and when to split a script, client- and server-side performance practices, monitoring governor limits with trace flags and debug logs, accessibility and configuration practices, and Type, SubType and Language naming.

Official exam objective
Describe best practices for Omniscripts.

~7 min read · 8 practice questions ·

What the exam expects

  • Apply the Omniscript recommended limits and read Design Assistant's informational and warning icons.
  • Recognise the 4 MB LWC limit and split oversized Omniscripts.
  • Choose client- and server-side practices that cut roundtrips and payload size, including PDF template size.
  • Monitor governor-limit usage with trace flags and Apex debug logs.
  • Follow accessibility, configuration and naming practices, including the generated LWC name.

Key terms: Design Assistant (real-time design feedback in the Flexcard and Omniscript designers), recommended limit (a design threshold that triggers an alert, not a hard block), roundtrip (one client-to-server call), trace flag (the debug-log setting for a user), TypeSubtypeLanguage (the Omniscript's unique identifier and LWC name).

Key facts

Action Blocks
Detail
6 recommended, 10 maximum; info icon at 7, warning at 10
Omniscript LWC size
Detail
Over 4 MB shows "inactive or isn't deployed" in Preview
Elements per Omniscript
Detail
At most 750
PDF template
Detail
Over 250 KB slow; over 1 MB can take minutes or time out
Several actions between steps
Detail
Combine into one Integration Procedure
Governor-limit monitoring
Detail
Trace flag on the running user, then Apex debug logs
Table-mode Edit Blocks
Detail
Not screen-reader compatible; use Flexcard data tables
Type and SubType
Detail
Letters and numbers; no spaces or underscores; 104 characters maximum
Sources for this section (5)
  • Why does Help discourage assigning a ContextId inside an Omniscript?
  • When can merging saved data duplicate Edit Block entries?
  • Why can't an Omniscript use the underscore join that Integration Procedures use?
  • Why should validations run on the current step?

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 (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 Developer exam