Omnistudio Fundamentals18% of the exam
Salesforce CLI, Build Tool, IDX Workbench and migration
Which deployment tool fits each Omnistudio runtime, how Build Tool jobs and IDX Workbench move DataPacks on the Managed Package Runtime, how Salesforce CLI, the Omnistudio Metadata setting and Clean Metadata Deployment work on the Standard Runtime, plus data-tree export and import and installing the Migration Assistant.
Describe the tools required to complete the end-to-end implementation process (SFCLI, VBT, Migration, etc.).
~8 min read · 11 practice questions ·
What the exam expects
- Choose the deployment tool from the runtime and data model of the source and target orgs.
- Read a Build Tool job in a CI script and know what IDX Workbench adds and doesn't.
- Configure Salesforce CLI deployment on the standard runtime: the Omnistudio Metadata setting, separate setup-object deployments, and Clean Metadata Deployment's metadata types and version behaviour.
- Export and import components with Salesforce CLI data-tree commands and with data packs, including what converts between runtimes.
- Install and run the Migration Assistant as part of the development lifecycle.
Key terms:
- DataPack: a bundle of Omnistudio components and related items moved as data between orgs.
- Omnistudio Build Tool (formerly Vlocity Build Tool, VBT): Node.js command-line tool that deploys DataPacks from a YAML job.
- Omnistudio Metadata: the setting that enables Metadata API for Omnistudio standard objects.
- Clean Metadata Deployment: the setting that turns Omnistudio components into standard setup metadata.
Key facts
CLI scope
- Detail
- Standard objects in source; standard objects and standard runtime in target
Mixed deployments
- Detail
- Setup objects and OmniProcess/OmniUICard can't deploy together
Managed package tools
- Detail
- Build Tool (formerly VBT) or IDX Workbench; data packs for simple cases
CI on managed package
- Detail
- Build Tool for scripts or Jenkins
Omnistudio Metadata
- Detail
- Required for Metadata API; can't be disabled
Clean Metadata API version
- Detail
- New metadata types require API 67.0 or later
Both orgs
- Detail
- Turn on Clean Metadata Deployment in source and target
Version state
- Detail
- Active deploys as active, inactive as inactive
Data-tree export
- Detail
- Omit isActive; import fails with isActive=true
Migration Assistant
- Detail
- SF CLI plugin @salesforce/plugin-omnistudio-migration-tool
Sources for this section (9)
- Tool Considerationshelp.salesforce.com (opens in a new tab)
- Deploying Omnistudio Componentshelp.salesforce.com (opens in a new tab)
- IDX Workbenchhelp.salesforce.com (opens in a new tab)
- Data Mapper Versioninghelp.salesforce.com (opens in a new tab)
- Clean Metadata Deploymenthelp.salesforce.com (opens in a new tab)
- Set Up Clean Metadata Deploymenthelp.salesforce.com (opens in a new tab)
- Clean Metadata FAQshelp.salesforce.com (opens in a new tab)
- Export and Import Omniscriptshelp.salesforce.com (opens in a new tab)
- Migration Assistant blogdeveloper.salesforce.com (opens in a new tab)
- Why does an import of an exported Omniscript fail when the JSON carries isActive=true?
- When can data packs from a managed package org be imported into a standard org?
- Which setting must be on before Metadata API can deploy Omnistudio standard objects?
- Why does a deployed component's existing active version in the target become inactive under Clean Metadata Deployment?
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 (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams