Omnistudio Frequently Asked Questions (FAQs)

What is the Omnistudio standard designer?

The Omnistudio standard designer operates directly within the Salesforce Platform infrastructure, rather than through a managed package. Standard runtime refers to the runtime components of Flexcards, Data Mappers, Integration Procedures, and Omniscripts operating on the Salesforce Platform.

What are the advantages of using the standard designer?

Using the standard designer offers several advantages:

• Improved performance and a more robust user experience.
• Instant activation for Omniscripts, Integration Procedures, and Flexcards.
• Enhanced list pages built based on Salesforce standards, with better performance.
• A dedicated Manage Versions page for easier version comparison and switching.
• Intuitive canvas experience with easier element searching and consistent left-to-right drag-and-drop functionality.
• Simplified process for creating and activating Flexcards.

What changes are in the Integration Procedure standard designer?

The Integration Procedure standard designer features:

• An intuitive layout.
• Easier insertion of actions following the industry builder framework.
• A designer experience that's consistent with Salesforce design and user experience principles.
• A requirement to save after each edit for functional benefit.
• Flexibility to rearrange the order of steps right within the canvas.

Is the Omnistudio app available with the standard designer?

Yes. However, it is recommended that you search for the required Omnistudio component directly rather than the app. This provides better performance and loads your list views faster. If you're an admin, it is recommended that you restrict the user profiles that can search for the Omnistudio app, thus making component search the default usage pattern. For more information, see Hide the Omnistudio App While Using the Standard Designer .

What changes are in the Data Mapper designer?

The Data Mapper standard designer provides:

• Simplified mapping functionality.
• A simplified layout.
• Easy insertion of steps.
• Flexibility to rearrange the order of steps right within the canvas.

How can I tell if my org is using standard runtime or standard designer?

Navigate to Setup, use Quick Find to search for Omnistudio Settings. Check the settings for Managed Package Runtime and Managed Package Designer. If a setting is on, it means that the runtime or designer are on the managed package.

Is some functionality not supported in the standard designer?

Exporting and importing directly from the standard designer using data packs isn't supported; use Salesforce CLI instead.

Is OmniOut supported with standard designer?

No, OmniOut is not supported. To use OmniOut, install a managed package in your org, and use the managed package designer.

Who is considered a new customer?

New customers are those who haven't installed Vlocity packages (vlocity_cme, vlocity_ins, vlocity_ps). They also don't have the Omnistudio package or Omnistudio licenses enabled.

Who is considered an existing customer?

Existing customers have installed Vlocity packages (vlocity_cme, vlocity_ins, vlocity_ps), the Omnistudio package, or have Omnistudio licenses enabled.

If I'm a new customer starting with Summer ’25, is installing a package necessary to use Omnistudio standard designer?

No. For new customers, enabling the Omnistudio License provides standard designer and standard runtime by default. However, if you plan to use the OmniOut functionality, you still need to install a managed package.

If I'm an existing customer with a managed package installation, what is the process to use the standard designer?

First, enable the Omnistudio license. Then, install the latest package. If you're on the managed package runtime, migrate to the standard runtime. After this, the standard designer and standard runtime are available.

I was already using the standard runtime in Spring ’25 (or earlier). What happens when I upgrade to the Summer ’25 package?

The Omnistudio standard designer is the default designer in your org.

I've been using the managed package designer and runtime. What happens when I upgrade to the Summer ’25 package?

There is no change in this scenario. If the runtime was pointing to the package before the upgrade, the designers will also continue to point to the package after upgrading to Summer ’25.

Can I switch back to using the managed package designer after moving to the standard designer?

Yes, an administrator can navigate to Setup > Omnistudio Settings and toggle the Managed Package Designer setting back to On.

What happens if I switch from the standard designer back to the managed package designer?

Components created or edited using the standard designer may not open correctly in the managed package designer due to compatibility differences. It's recommended to create new versions when switching.

I’m an existing customer who upgraded to Summer ’25 with the managed package runtime. Can I choose to use the standard designer?

Yes. You'll be on the managed package designer and runtime by default. However, you can switch to the standard designer by turning off the Managed Package Designer setting. It's crucial to test this thoroughly in a sandbox environment first before enabling standard designer in production orgs.

If I had the managed package runtime enabled in Spring ’25, can I use the standard designer after upgrading to Summer ’25?

To enable standard designer, the org must first be using standard runtime. Before switching the standard runtime, consult with your account executive or cloud team to ensure there are no dependencies. Once on standard runtime, you can then enable the standard designer.

If I have enabled an Omnistudio license in Spring ’25 without a package installation, will I be upgraded to the standard designer in Summer ’25?

No, unless you had requested ‌and used ‌the Omnistudio standard designer in Spring ’25. In Spring ’25, the standard designer was available on request from Salesforce Customer Support.

You can either install a Summer ’25 package or request ‌the standard designer from Salesforce Customer Support.

What is the recommended best practice for moving to the standard runtime after upgrading to Summer ’25?

If your workflows rely heavily on existing configurations and you were previously using the standard runtime, it's recommended that you first turn on the managed package runtime after the Summer ’25 upgrade. Then, follow these steps.

• Clone an org that has been upgraded to Summer ’25. See Test the Standard Designer in a Cloned Org.
• In the cloned org, enable the standard designer.
• Thoroughly test all critical flows and components in the cloned org to verify that they function correctly with the standard designer.
• If testing is successful, you can then enable standard designer in your production org.

Alternatively, you can create a new version of the component you want to test and verify that all workflows work as expected. For instance, if you want to test an Omniscript that has ten versions and version 9 is the current active version, follow these steps.

1. Turn on the Managed Package Designer setting.
2. Clone version 9 of the Omniscript, which gives you version 11.
3. Turn off the Managed Package Designer setting.
4. Verify that version 11 of your Omniscript works as expected with the standard designer.

If your Omniscript works correctly, you can then enable the newly created version where needed.