Omnistudio Fundamentals18% of the exam
Standard Runtime, Managed Package Runtime and upgrades
What separates the Omnistudio Standard Runtime from the Managed Package Runtime, how automatic and manual package upgrades work, what happens when you disable the Managed Package Runtime setting, and which Migration Assistant steps are automated or stay manual.
Explain Managed Package Runtime vs. Standard Runtime, Automatic Upgrades, and Manual Intervention Upgrade.
~8 min read · 10 practice questions ·
What the exam expects
- Distinguish the Standard Runtime (standard objects) from the Managed Package Runtime (custom objects) and name the features only one of them supports.
- Explain automatic upgrades for Spring '24 and later installs, the manual upgrade path, and the package-free start for new customers.
- Configure the move: disable the Managed Package Runtime setting, handle pages that still load generated custom components, and set the field-level security the standard runtime enforces.
- Separate Migration Assistant tasks that are automated from those that stay manual, and handle Assess-mode findings.
- Modify shipped standard content and replace managed-package-only Apex and settings.
Key terms:
- Standard Runtime: Omnistudio running on standard objects (OmniProcess, OmniUiCard, OmniDataTransform).
- Managed Package Runtime: the runtime of the Vlocity or Foundation managed package; supports the custom data model.
- Automatic upgrade: major and patch releases delivered at each seasonal release.
- Omni Interaction Config: the Setup records that hold standard runtime settings.
Key facts
Automatic upgrades
- Detail
- Spring '24 or later installs get major and patch upgrades automatically
Manual upgrade
- Detail
- Installation URL on Omnistudio Managed Package Releases
New customers
- Detail
- From Summer '25, standard designer and runtime by default; don't install the package
One-way switch
- Detail
- Don't re-enable Managed Package Runtime after disabling it
Required FLS
- Detail
- Omni Process Compilation (Read, Edit), Omni Data Transformation (Read), Omniscript Saved Sessions (Read, Edit)
Old custom components
- Detail
- Replace with standard components, or enable Deploy Custom Lightning Web Components in Standard Runtime
Scale Cache
- Detail
- Can't be cleared; TurnOffScaleCache = true turns it off
Apex interface
- Detail
- System.Callable replaces VlocityOpenInterface
Shipped content
- Detail
- Create a version of the standard component (Winter '23 on)
Manual migration tasks
- Detail
- Angular conversion, Business Rules Engine migration, custom LWC deployment
Sources for this section (6)
- Install or Upgrade the Omnistudio Packagehelp.salesforce.com (opens in a new tab)
- Omnistudio Settingshelp.salesforce.com (opens in a new tab)
- Disable Managed Package Runtimehelp.salesforce.com (opens in a new tab)
- Supported Featureshelp.salesforce.com (opens in a new tab)
- Omnistudio Differenceshelp.salesforce.com (opens in a new tab)
- Migrate to Standard Runtimehelp.salesforce.com (opens in a new tab)
- Why can Assess mode be rerun until the report is clean without risk to the org?
- Why shouldn't the Insurance or CME package be installed on an org that has the Foundation package?
- Which second setting do you disable to open the standard designer?
- When should you not assume the standard designer switch is automated?
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