Maintain Your Omnistudio Developer Certification for Summer ’25

Learning Objectives

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

Describe how to use the Omnistudio list view to search, filter, and manage component records in the standard designer.
Describe the benefits and capabilities of the Omnistudio Standard Designer.
Describe how Connect APIs improve Apex-to-Omnistudio integration.
Identify where the Lightning Rich Text Editor can be used in Omniscripts and Flexcards.
Explain how to enable and use error logging.
Demonstrate how to configure a Data Mapper Load using external data sources.

Maintain Your Certification

If you hold the Omnistudio Developer certification, keep in mind that you need to complete this module by the due date to maintain your certification.

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

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

Protect the Integrity of Your Certification

The quality of our certification exams and the value that they provide are our highest priority. Protecting the security and confidentiality of our exams is essential to providing our customers with certifications that are respected and industry-leading.

As a participant of the Salesforce Certification Program, you’re required to accept the terms of the Salesforce Certification Program Agreement. Please review the Salesforce certification exam-taking policies in the Salesforce Certification Program Agreement and Code of Conduct Trailhead Help article for more details.

Salesforce introduced great feature enhancements over the past year. Take a look at some of the more important ones.

Build Omnistudio Components with the Standard Designer

Salesforce has introduced the Omnistudio Standard Designer—an intuitive, modern interface for building and managing Flexcards, Omniscripts, Integration Procedures, and Data Mappers. Designed to replace the older, managed package-dependent tools, this new designer streamlines development and is now the recommended approach for teams using the standard runtime.

Built on Lightning Web Components, the Standard Designer provides a faster, more efficient experience. Developers benefit from a clean UI, real-time feedback, drag-and-drop functionality, and improved component activation speeds. For example, Omniscript and Flexcard activations are now up to 6–7 times faster, and elements can be edited in place without switching tabs. Integration Procedures and Data Mappers also see notable speed and usability improvements.

Beyond speed, the Standard Designer reduces reliance on legacy managed packages, aligning with the strategic direction at Salesforce. It offers consistent workflows across component types and introduces tools like the Omnistudio Design Assistant, which gives feedback on component health, performance, and best practices during the build process.

The Standard Designer is available in Lightning Experience, Experience Cloud sites, and Enterprise, Performance, and Unlimited Editions—provided Omnistudio and the standard runtime are enabled.

To use the Standard Designer, keep in mind that you have to disable Managed Package Runtime. Learn more in the Migration Process from Omnistudio for Managed Packages to Omnistudio. Note that once you open a component in the new designer, you won’t be able to edit that same component in the Managed Package Designer—even if it originally appeared first in the List View.

With its improved usability and performance, the Omnistudio Standard Designer helps teams create components up to 10-times faster than before, while aligning with the Salesforce long-term goal of simplifying development through standard, package-independent solutions.

Browse and Manage Omnistudio Components with the List View

Omnistudio now includes enhanced list view pages for Flexcards, Omniscripts, Integration Procedures, and Data Mappers, creating a streamlined user experience and improved performance. When using the standard designer—enabled by default in Summer ’25—you can view and open components directly from the list view.

From the list view, you can:

Create an Omnistudio component.
Search, filter, and save your preferred list views.
View the last modified version of a component.
View all versions of a component in a new page.
Activate, deactivate, or delete a component.

While you can’t import or export components from the list page, Salesforce CLI remains the recommended method for those tasks. Each list view can display up to 2,000 records. If you need to view additional records, use filters, sort, or search to refine your results.

Remove Duplicate Tabs

To improve your workspace after enabling the Standard Designer, it’s recommended to remove any duplicate component tabs from the App Launcher. These duplicates can appear for users with the System Administrator profile and should be hidden to avoid confusion. Follow these steps to clean up your tabs.

From Setup, in the Quick Find box, search for and select Profiles.
Edit the System Administrator profile.
In Custom Tab Settings, select and hide the duplicate component tabs.
Click Save.

Component List View

To access the list view for a component, go to the App Launcher and select one of these: Flexcards, Omniscripts, Integration Procedures, or Data Mappers. Once you're in the list view, you can create custom filters to narrow down your results.

Click Filter.
Click Add Filter and set the filter criteria.
Click Filter Logic to add conditions. Use the numbers assigned to each filter to build logic statements.
Click Save.

If you want to load a filtered view by default, pin it using the Pin list view option. You can also use the List view controls to create or customize views. To open a component in a new browser tab, simply click the record. A column labeled Managed Using Standard Designer lets you know whether the component is managed with the Standard or Managed Package Designer.

View Component Versions

Important: Once you open a component in the standard designer, it can no longer be edited in the managed package designer—this change is permanent. The component will still run as expected at runtime, but any further edits must be made in the standard designer. This has significant implications for orgs using managed package designers, so review carefully before proceeding.

To view all versions of a component, click Versions or select Manage Versions from the row’s dropdown menu. Choose any version from the list to open it in the standard designer.

These list view enhancements support Lightning Experience, Experience Cloud sites, and all Enterprise, Performance, and Unlimited Editions where Omnistudio is enabled. They’re only available for customers using the standard designer package.

Optimize Apex-to-Omnistudio Calls with Connect APIs

Salesforce continues streamlining the Omnistudio developer experience by reducing dependencies and improving performance. One of the major enhancements in this area is the introduction of Connect APIs, which lets you invoke Data Mappers and Integration Procedures from Apex classes. These APIs eliminate the need for the managed package and improve performance when making calls from Apex.

Previously, calling Integration Procedures or Data Mappers from Apex required a dependency on the Omnistudio managed package. For teams transitioning to the standard runtime, this added complexity and potential performance bottlenecks.

With Connect APIs, developers can improve execution speed, remove reliance on legacy dependencies, and align with the Salesforce roadmap for lightweight, scalable Omnistudio architecture. The new Connect APIs represent a major improvement in performance and maintainability for Apex-based calls to Omnistudio components. Developers using the standard runtime should prioritize migrating to this approach to remain aligned with /Salesforce best practices and to future-proof their solutions.

To take full advantage of this update, you must be using the standard runtime.

The change applies to Lightning Experience, Experience Cloud Sites, and Enterprise, Performance and Unlimited Editions (with Omnistudio enabled).

Use the Lightning Rich Text Editor in Omniscripts and Flexcards

To format text in Omniscripts and Flexcards, use the Lightning Rich Text Editor. This editor replaces TinyMCE in the Omnistudio standard designer and supports rich formatting, real-time preview, and media.

You can use the‌ following.

Lightning Rich Text Editor with these Omniscript elements:
- Step with Instruction property
- Disclosure with Text property
- Text Block with Text property
Editor with the Display Text element in Flexcards with the Text property

This change applies to Lightning Experience, Experience Cloud sites, and Enterprise, Performance, and Unlimited editions with Omnistudio. It’s for Omnistudio customers using standard runtime and Standard Designer with the latest core and managed package versions.

Troubleshoot Integration Procedures by Analyzing Error Logs

Effective troubleshooting is essential for maintaining reliable Omnistudio integrations. That’s why Salesforce has introduced enhanced error logging for Integration Procedures, making it easier to diagnose and resolve issues by capturing detailed error data during runtime.

When enabled previously, diagnosing failures in Integration Procedures often required manual debugging, since error messages weren’t always detailed or persisted. With the new logging feature, error details are written to the OmniComponentErrorLog object, which helps surface previously hidden errors and simplifies root cause analysis. As a result, you:

Gain visibility into which steps failed and why.
Can retain logs for auditing or post-deployment review.
Minimize the time spent troubleshooting in complex flows.

This change applies to Lightning Experience, Experience Cloud Sites, and Enterprise, Performance, and Unlimited Editions (with Omnistudio enabled). It applies only to customers using the standard runtime and standard designers.

Once the feature is enabled, logs are stored in the OmniComponentErrorLog custom object. To activate error logging for Integration Procedures:

From Setup, in the Quick Find box, search for Omni Interaction Configuration.
Click New Omni Interaction Configuration.
Set the Name and Label to ErrorLoggingEnabled.
Enter True as the value.
Click Save.

When a step fails, the error details and response are logged in the Input field of the OmniComponentErrorLog sObject. The ErrorMessage field captures the error message, including any custom messages you choose to send.

To view detailed information about failed Integration Procedure steps:

In Setup, go to Users | Profiles.
Select a profile.
Under Tab Settings, set Omni Component Error Logs to Default On.
Use the App Launcher to open Omni Component Error Logs.

The new error logging capability offers Omnistudio developers powerful insight into Integration Procedure failures. By enabling this feature, teams can improve system reliability, accelerate debugging, and gain a better understanding of complex runtime issues—all without additional custom instrumentation.

Use External Data Sources in a Data Mapper Load

Integrating external data into Salesforce processes has historically required custom code or complex middleware. With updates to Omnistudio, you can now include external data in Data Mapper Loads, streamlining data flows and ensuring the data aligns with Salesforce record structures.

To use external data, you need to create a custom interface object and map external fields to corresponding Salesforce fields via Data Mapper Load. Here’s how to get started:

Create an interface object that you can use to map external data to a corresponding Salesforce sObject.
Add fields to the interface object that match the data structure of the external source.
Create a Data Mapper Load.
Set the input type to sObject.
Select the interface object as the source.
Map the fields from the interface object to the appropriate Salesforce records.

By allowing the use of external data as input in Data Mapper Loads, Salesforce gives Omnistudio developers a more powerful and flexible way to integrate external sources into the Salesforce ecosystem. This feature promotes cleaner architecture, reusability, and reduced technical overhead.

This feature is available for Lightning Experience, Experience Cloud Sites, and Enterprise, Performance, and Unlimited Editions with Omnistudio enabled. It applies only to customers using the standard runtime and standard designers.

Continue to the next unit to learn about more new features and updates to Omnistudio Developer.

Tempo stimato

Argomenti

Hai bisogno di aiuto?

Risorse per Salesforce Platform