Maintain Your Omnistudio Consultant Certification for Summer ‘26

Learning Objectives

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

Embed Flexcards and Omniscripts on Lightning Web Runtime sites.
Explore updates to Data Mapper that include using the IS NULL operator and version control enhancements.
Enhance data consistency with Omni Global Auto Number.
Ensure stricter security with enhanced security checks.
Experience a better user experience with enhanced save for later, accessibility improvements, and error guidance.

Stay Current with Your Certification

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

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

While anyone can earn this badge, it is designed for those who hold the Omnistudio Consultant 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 Consultant Overview

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

Design solutions using Omnistudio tools that meet customer business requirements, can be maintained and scaled, and contribute to long-term customer success.
Consult on digital transformation projects that rely on Omnistudio tools.
Apply the Omnistudio solution to common customer use case scenarios in different industries.
Determine a project's needs by evaluating a customer's requirements, assumptions, risks, and constraints.

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

Flexcards and Omniscripts on LWR 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. The ability to embed Flexcards and Omniscripts on LWR Experience Cloud sites is now fully available, allowing a user to render faster and scale better with fewer limitations.

Invoke Autolaunched Flows in Flexcards (Pilot)

You’re now able to reuse existing business logic across automation tools by using Flows in Flexcards. This streamlines your development process by using autolaunched flows as a native data source in Flexcards.

There are two ways to set this up. You can either:

Select Autolaunched Flow as a data source in the Flexcard’s Setup tab.
Alternatively, add an Action element, set the Action Type to Data, and select Autolaunched Flow as the data source type.

Autolaunched Flows in Flexcards is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer's sole discretion.

Data Mappers

The latest changes to Data Mappers include version control enhancements and introduce the new IS NULL operator. Review how these affect Omnistudio Consultants and help simplify processes.

Introducing the IS NULL operator

Get null values easily with the newest tool in Omnistudio Data Mapper Extract and Turbo Extract. The new IS NULL operator filters null or empty records, keeping your data more organized. Previously, the quality operator (=) didn’t consistently handle null filtering, often requiring complex workarounds. The IS NULL operator supports explicitly filtering blank fields, without adding an additional condition.

Data Mapper Versioning

You can now enable version control for Data Mappers to create new versions instead of overwriting active components, keeping 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, keeping Data Mappers consistent with other Omnistudio components.

Here’s how to enable Data Mapper versioning

To enable Data Mapper versioning, enable the Omnistudio Metadata setting first. 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, 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.

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 (like 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.

Enforced Security Checks

Security settings have been strengthened for customers using Omnistudio, enforcing stricter validation of access and permissions. Omnistudio now enforces advanced security settings to protect data and maintain system integrity. These enforced security checks ensure that users have the appropriate access to objects and fields used within Omnistudio components, and only through authorized, secure channels. The controls affect guest, registered, authenticated, and non-authenticated users. Learn more by reviewing the field-level security requirements for standard runtime in the help article, Security Checks for Omnistudio.

Enhanced Save for Later

Deliver seamless, collaborative customer journeys where different users can start, save, and resume the same Omniscript. We’ve 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—as can customers and employees. Learn how to save and resume an Omniscript, configure save options, and map saved instance URLs to customer fields.

Accessibility Enhancements

Deliver more inclusive digital experiences and user interfaces with comprehensive accessibility, usability, and consistency enhancements across Omnistudio runtime components and Flexcard and Omniscript elements. These enhancements cover many accessibility requirements, such as enhanced screen reader announcements, easier navigation, and a more powerful UI experience.

Enhancements organized by release

These improvements provide clearer feedback, enhanced visual contrast, and more reliable interactions for users of assistive technology. Some enhancements are only available when you turn on the Runtime Accessibility setting in the Flexcard and Omniscript designers, while other updates are automatic. Review the details around each release for more information:

Release	Enhancements	Action
Winter ‘26	Improved accessibility of Flexcards and Omniscripts features: Step Chart, Currency, URL, Multiselect, Date, Time, Block, and Password elements	No action needed
Winter ‘26	A new accessibility option, Announce when the block is selected, has been added to the properties of the Flexcard Block element to improve support for screen reader users	No action needed
Winter ‘26	Multiple enhancements to the TypeAheadbBlock of an Omniscript	No action needed
Spring ‘26	Improved semantics, enhanced navigation, better visual feedback	May have to toggle Runtime Accessibility
Spring ‘26	Changes to Radio, Radio Group, Block, Typeahead, custom attributes, disabled property for inputs, and Action	May have to toggle Runtime Accessibility
Summer ‘26	Multiple Omniscript enhancements	May have to toggle Runtime Accessibility
Summer ‘26	Multiple Flexcard enhancements	May have to toggle Runtime Accessibility

Actionable Guidance for Errors

Understand error messages as soon as they appear with new Omnistudio guidance. You’ll now see actionable causes and solutions for errors so you can easily fix issues related to component design, runtime performance, access, and other commonly-faced scenarios. You’ll see error messages, potential causes, and potential solutions for the following categories in this help article, Common Errors and Resolutions in Omnistudio.

System errors
Omniscript errors
Flexcard errors
Integration procedure errors
Data Mapper errors
OmniAnalytics Errors

In this unit, you learned about some of the most important Omnistudio Consultant 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 Consultant certification.

Estimación de tiempo

Temas

¿Necesita ayuda?

Recursos de Headless 360 Platform