You are here:
Differences Between Omnistudio and Omnistudio for Managed Packages (Managed Package)
For the managed package runtime, Omnistudio and Omnistudio for Managed Packages differ in a few ways, but the key differences are the data models, the features available in each, and how you access each suite depending on your org licenses. Think of Omnistudio and Omnistudio for Managed Packages as two versions of an application suite, not two types of packages. While Omnistudio uses the standard object model, Omnistudio for Managed Packages uses the custom object model. That difference is why the two versions don’t have exactly the same features.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Omnistudio for Managed Packages (Custom Objects)
Omnistudio for Managed Packages is the original version of a set of services, components, and data model objects used to create Industry Cloud apps by setting up guided interactions using data from your Salesforce org and external sources. Some of the features in Omnistudio for Managed Packages include the original Angular Vlocity Cards and Omniscripts (Angular was supported until December 31, 2022), LWC Omniscripts and LWC Flexcards, Vlocity Interaction Launcher, Omnistudio Data Mappers, Integration Procedures, and Calculation Procedures and Matrices.
Omnistudio for Managed Packages features are available as part of an Industries managed package (Health and Insurance, and Communications, Media, and Energy) and are built with custom objects.
Omnistudio (Standard Objects)
Beginning Summer '21, some of the Omnistudio for Managed Packages features were built using the standard data model. Instead of using custom objects, the features use standard objects. Features in the Omnistudio application suite are Flexcards, Omniscripts, Data Mappers, Integration Procedures, Business Rules Engine (which replaced Calculation Procedures and Matrices in Winter '22), and, with the right license, Document Generation. Not all Omnistudio for Managed Packages features are available in Omnistudio. See Supported Features in Omnistudio and Omnistudio for Managed Packages.
Omnistudio includes these standard Omnistudio features. However, if you have an Industries managed package but want to take advantage of features only available with the Omnistudio, you must get the Omnistudio license. If you installed Omnistudio and Salesforce Industries packages in that order, Omnistudio features are accessible, with a few exceptions. See OmniStudio-First Side-by-Side Package Installation Results.
Comparison of Omnistudio with Omnistudio for Managed Packages
Omnistudio (uses standard objects) |
Omnistudio for Managed Packages (uses custom objects) |
|
|---|---|---|
Packages |
To view, create, and modify content using the Omnistudio designers in standard runtime, your org must have the Omnistudio package or an Industry managed package with an Omnistudio license installed. See Standard Omnistudio Content and Runtime. |
To view, create, and modify Omnistudio for Managed Packages content, you must have an Industries managed package installed. Omnistudio for Managed Packages products ship with Industries managed packages. |
Available products and supported features |
See Supported Features in Omnistudio and Omnistudio for Managed Packages. |
See Supported Features in Omnistudio and Omnistudio for Managed Packages. |
Objects |
Omnistudio products use standard objects, which are included with Salesforce by default. See What’s the Difference Between Standard and Custom Objects?. |
Omnistudio for Managed Packages uses custom objects, which extend standard functionality and store information that’s unique to an org. See What’s the Difference Between Standard and Custom Objects?. |
Object Names and Descriptions |
||
Omnistudio Configuration Settings |
Enable or disable Omnistudio feature settings in Setup > Omni Interaction Config. |
Enable or disable Omnistudio for Managed Packages feature settings in Setup > Custom Settings. |
Omnistudio Metadata API Support |
Enable Omnistudio Metadata API support to retrieve and deploy Omnistudio content with Salesforce DX CLI and the Ant Migration Tool. Spaces and special characters aren't supported. Before you deploy data packs in Omnistudio orgs where Omnistudio metadata is enabled, make sure that the object names, Types, and SubTypes are alphanumeric. |
Not applicable. |
Adding Custom Content |
Not applicable |
When the Managed Package runtime is enabled:
|
Adding and Viewing Standard Content |
In the standard runtime, use the standard Omniscript and Flexcard components available in the Lightning App and Experience Builders. See Standard Omnistudio Content and Runtime. |
Not applicable. |
Modifying Standard Content |
Beginning in Winter '23, to modify a standard component that ships with your Industries license, create a version of the component. |
You can clone and modify custom components that ship with your Industries license. |
- Does Your Org Use Custom or Standard Objects? (Managed Package)
For the managed package runtime, to determine whether your org uses Omnistudio standard objects or Omnistudio for Managed Packages custom objects, go to Setup and find Omni Interaction Configuration. - Supported Features in Omnistudio and Omnistudio for Managed Packages (Managed Package)
For the managed package runtime, this page lists the differences in the available components and supported features in Omnistudio and Omnistudio for Managed Packages. Omnistudio for Managed Packages components are built using custom objects in the Omnistudio managed package runtime. Omnistudio, which uses Salesforce standard objects and the Omnistudio standard runtime, doesn’t support all the features available in Omnistudio for Managed Packages components. - Which Version of Omnistudio Do You Have? (Managed Package)
For the managed package runtime, determine which version of the Omnistudio application suite you’re using. The name of the managed package you installed may not correspond to Omnistudio or Omnistudio for Managed Packages.
