Omnistudio Developer Certification Maintenance (Summer ’26)

Learning Objectives

After completing this unit, you’ll be able to:

Take advantage of enhancements to existing processes, testing, and tools around Flexcards and Omniscripts.
Enable and set up new features including Omnistudio Migration Assistant and Omni Global Auto Number.
Manage components with Omnistudio Hybrid.

Stay Current with Your Certification

Salesforce certifications hold the most value when you keep them relevant. To keep your Omnistudio Developer certification current, complete this badge by the due date.

Interested in learning more about getting certified? Check out the Omnistudio Developer certification.

While anyone can earn this badge, it is designed for those who hold the Omnistudio Developer certification.

As part of the Salesforce Certification Program, you agree to the terms of the Salesforce Certification Program Agreement. Review the exam policies in the agreement and the Salesforce Certification Program Agreement and Code of Conduct article before you continue.

Omnistudio Developer Overview

As an Omnistudio Developer, you deliver the best value when you:

Design and configure cloud applications that solve complex business challenges.
Build and customize applications on the Salesforce Platform.
Use a combination of programmatic and declarative skills to extend and customize applications.
Configure defined business requirements into declarative technical solutions.

This badge highlights key updates you need to know for Omnistudio Developer Summer ’26 to keep your certification current and your skills sharp.

Omnistudio Migration Assistant

With Omnistudio Migration Assistant, a new Salesforce CLI plugin, it’s easier than ever to migrate from the custom data model to the standard data model and standard runtime. It automates and simplifies the migration of components such as Flexcards and Omniscripts. Your new assistant handles complex migration tasks while ensuring configuration consistency across environments, which reduces manual effort and saves time. Streamline and accelerate your migration process seamlessly. The tool offers these key benefits.

Replaces legacy wrappers with standard runtime wrappers
Updates namespace references and cleans record names automatically
Converts Omnistudio components from the custom data model to the standard data model
Validates components with built-in checks and detailed assessment and migration reports
Identifies and lists components that are ready for migration, require manual action, or are skipped or failed

Omni Global Auto Number

Stay organized by simplifying the autogeneration of numbering with the Omni Global Auto Number. In order to enhance data consistency and efficiency, this feature allows you to design consistent, customized numbering systems for specific business records such as sales orders or loan applications.

How to Configure and Use Omni Global Auto Number

Go to App Launcher.
Find and select Omni Global Auto Number.
Select New.
Modify the values to fit your business needs by setting the attributes and values.
Use the GLOBALAUTONUMBER function in Omnistudio Data Mappers or Integration Procedures.

Flexcards and Omniscripts on Lightning Web Runtime Sites

Create faster guided interactions for your users with the combined power of Lightning Web Runtime’s (LWR’s) speed and Omnistudio’s customization capabilities. Embed Flexcards and Omniscripts on LWR Experience Cloud sites for faster rendering and better scalability.

Want to do more research before you get started? Learn how to activate and publish a Flexcard to a Lightning page or a page in an Experience Builder site. Or review detailed instructions on how to add your Omniscript to an Experience Cloud Page, and read considerations for using Omnscripts with LWR sites.

UI Testing Automation

Validate full user journeys exactly as they appear on screen and enjoy improved deployment reliability by automating testing for Omniscripts and Flexcards. Automated testing is crucial for ensuring the stability and integrity of Omnistudio deployments. You can now write UI-driven tests to validate end-to-end workflows for Omniscripts and Flexcards using the UI Test Automation Model (UTAM) framework. The UTAM framework interacts directly with the interface to test user inputs, navigation, actions, data rendering, and visual states. Learn how to set it up and automate UI testing for Omniscripts and Flexcards.

Benefits of UTAM Testing

UTAM testing provides several key advantages for quality and stability.

Durable and reliable UI testing: Your tests remain stable and reliable even when platform updates change the component structure. UTAM achieves this durability through document object model abstraction, which separates the test logic from the UI code.
Comprehensive user-journey validation: It tests Omniscripts and Flexcards end-to-end by simulating real user actions (form entries, button clicks, data checks, and conditional steps) and navigation.
Reusable and maintainable tests: It uses the page object model to organize UI test code into reusable Page Objects, which makes tests easier to read, build, and maintain.

Enhanced Save for Later

Deliver seamless, collaborative customer journeys where different users can start, save, and resume the same Omniscript. Salesforce removed limitations around Save for Later that often resulted in restrictions of its usage. You can now share Omniscript saved session records with the Sharing option, then resume Omniscripts across users with enhanced Save for Later. Now, both guests and registered users alike can work together, and so can customers and employees. To learn how to save and resume an Omniscript, configure save options, map saved instance URLs to customer fields, and more, check out Save and Resume an Omiscript.

Data Mapper Versioning

You can now enable version control for Data Mappers to create new versions instead of overwriting active components, which keeps your implementations consistent and neat. It activates existing standard Data Mappers as version 1 and locks active components to maintain consistency across your implementations. You can create new versions to make changes rather than editing active components, so Data Mappers remain consistent with other Omnistudio components.

Enable Data Mapper Versioning

To enable Data Mapper versioning, first enable the Omnistudio Metadata setting. This process validates your component naming conventions and fails if any names are invalid. Ensure that the Data Mapper names are alphanumeric and don’t include spaces or special characters.

Go to Setup in your org, and search for and select Omnistudio Settings.
If you haven’t already enabled Omnistudio Metadata API support, turn on the Omnistudio Metadata setting. After this setting is enabled, it can’t be disabled.
Check your email for confirmation that you’ve successfully enabled Omnistudio Metadata. If it fails, check that none of your component names have spaces or special characters.
Turn on Data Mapper Versioning from the same Omnistudio Settings page.

By default, Data Mapper versioning is disabled. You can turn off Data Mapper Versioning at any time.

Omnistudio Hybrid

With Omnistudio Hybrid, managed package users can now use both the managed package designer and the standard designer within the same org, which allows them to build new components on the standard runtime while maintaining legacy components. If you’re on a managed package runtime and designer, you can create all new components directly in the standard designer and standard runtime to experience a refreshed layout and improved performance.

Create components using Omnistudio Hybrid. Select the Managed Using Standard Designer option when creating Omnistudio components to build new components in the standard designer while you continue managing legacy components in the managed package designer.

By default, Omnistudio Hybrid is enabled for managed package users to maintain metadata consistency while providing a reliable path to modern workflows. Continue managing your existing legacy components in the managed package designer while building your new components on the standard designer.

Key Features

Object-level governance: Separate logic for standard and custom objects enables a modular digital transformation.
Runtime locking: After the Managed Package Runtime setting is disabled, the system locks into standard runtime mode to maintain metadata stability.
Designer flexibility: Switch between managed package and standard designers to resolve cross-dependency components before full deployment.

Use the Omnistudio Hybrid Compatibility Matrix to determine the active designer and runtime environment based on your org settings and object type.

In this unit, you learned about some of the most important Omnistudio Developer feature releases over the past few months. Now it’s time to test your understanding of these topics and complete the quiz to maintain your Omnistudio Developer certification.

Time Estimate

Topics

Looking for Help?

Headless 360 Platform Resources