Discover More Feature Enhancements

Learning Objectives

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

Explain how updating Node.js versions in OmniOut enhances security and performance.
Recognize the security and performance benefits of updating Node.js.
Identify the required tool versions and benefits of updating the Omnistudio deployment environment.
Explain how enhanced Apex class permission checks improve org security.
Explain why AngularJS-based Omniscripts are deprecated.
Explain how OmniOut enables developers to deploy Omniscripts and Flexcards outside of Salesforce.
Explain how the updated behavior of the Navigate Action element in Omniscripts enables more precise navigation between steps.

Continue to review some of the important feature enhancements that Salesforce introduced over the past year.

Secure Your Org by Updating Node.js Support in OmniOut

Security and performance are critical in any enterprise application stack. For this reason, Salesforce now supports Node.js versions from 18.20.4 to 22.11.0 for OmniOut, which help to enhance:

Security: Avoid vulnerabilities found in outdated Node.js versions.
Performance: Use performance improvements from the latest Node.js engine.
Future compatibility: Ensure your OmniOut scripts and build tools continue to function as the platform evolves.

This update is especially important for organizations that rely on OmniOut for packaging and deploy Omnistudio components across environments. It applies to Lightning Experience, Experience Cloud Sites, and Enterprise, Performance, and Unlimited Editions with Omnistudio enabled and available to Omnistudio customers using both the Managed Package Runtime and standard runtime.

To get started, existing OmniOut users can upgrade the npm packages by using the npm install command. If you’re new to OmniOut, follow these instructions to get started.

Securely Deploy Omnistudio Components with the Latest Build Tool and Node.js Versions

To deploy Omnistudio components, upgrade your Build Tool to a version later than 1.17.11 and Node.js to a version later than 18. This update also includes an upgrade of Puppeteer from version 5.3.1 to 21.11.0.

These upgrades modernize the deployment pipeline, align Omnistudio tooling with current web development standards, and deliver improvements in security, deployment reliability, and rendering and deployment speeds.

This change applies to Lightning Experience, Experience Cloud sites, and all versions of Enterprise, Performance, and Unlimited editions where Omnistudio is enabled. It’s relevant to developers using the Managed Package Runtime and the standard runtime.

Enable Apex Class Checks for Permission Sets and Permission Set Groups

Access control in Apex calls is essential for maintaining org-wide security. Salesforce has enhanced permission checks to include Apex classes assigned through permission sets and permission set groups, in addition to those assigned via user profiles. This improvement ensures more robust and comprehensive enforcement of Apex permissions when classes are invoked remotely.

In bulk implementations, the enhanced permission checks may lead to SOQL query limit errors. To avoid this, consider disabling the PerformAdvancedCheck flag. This limits checks to Apex classes assigned through the user’s profile only.

This update applies to Lightning Experience, Experience Cloud Sites, and Enterprise, Performance, and Unlimited Editions (with Omnistudio enabled). It’s available to customers using the Managed Package Runtime and the standard runtime.

When both the PerformAdvancedCheck and ApexClassCheck flags are enabled, the Apex class permissions checker evaluates Apex classes assigned through the user’s permission sets and permission set groups, in addition to those assigned via the user’s profile. If PerformAdvancedCheck is not enabled, the checker only evaluates Apex classes assigned to the user’s profile.

To enable the PerformAdvancedCheck flag:

From Setup, search for and select Omni Interaction Configuration.
Click New Omni Interaction Configuration.
Enter PerformAdvancedCheck as the name and label.
Set the value to OmniComponentErrorLog.
Click Save.

With advanced Apex class permission checks, you can now enforce a tighter and more flexible security model across your org. By including permission sets and groups in the access check, you align with modern Salesforce security practices while minimizing risk during remote Apex execution.

Migrate Legacy Omniscripts from AngularJS to LWC

Salesforce has officially ended support for AngularJS-based Omniscripts. To maintain compatibility and performance, all legacy Omniscripts must be migrated to the Lightning Web Component (LWC) framework. Designers and customers should update their Omniscripts to avoid relying on an outdated framework.

This change affects Managed Package Runtime customers. Our ongoing platform updates indicate that the legacy designer is likely to be deprecated entirely.

The deprecation reflects the broader Salesforce move away from outdated frameworks. AngularJS is no longer maintained by Google, making it a security and performance risk. By contrast, LWC offers faster load times, improved maintainability, and seamless integration with modern Salesforce development tools. Migrating to LWC not only ensures your Omniscripts remain supported but also future-proofs your implementation and improves the overall experience for users and developers.

This change applies to Lightning Experience, Experience Cloud sites, and all versions of Enterprise, Performance, and Unlimited Editions where Omnistudio is enabled.

Deploy Omniscripts and Flexcards Anywhere with OmniOut

Customers using standard runtime can now use OmniOut.

OmniOut extends the power of Omnistudio by enabling developers to run Omniscripts and Flexcards outside the Salesforce platform—on third-party websites or standalone web apps—without requiring complex integrations. It transforms standard components into reusable Lightning Web Components (LWCs) that you can deploy via your own CMS.

That means Omnistudio developers can extend digital experiences to broader audiences, reduce integration overhead, and align with modern web deployment practices. This flexibility empowers you to deliver Salesforce-powered interactions anywhere your users are—without being limited to Salesforce-hosted environments.

This feature is available in Lightning Experience, Experience Cloud Sites, and all editions where Omnistudio is enabled, for customers using the standard runtime and standard designer. OmniOut requires installation of a managed package and setup of a Node.js-based development environment (Node 18–22 supported).

To get started with OmniOut:

Download OmniOut: Get the static resource from Salesforce and open it in Visual Studio Code.
Install dependencies: Run npm install to set up the OmniOut project.
Add your component: Download your Omniscript or Flexcard LWC and add it to the OmniOut project.
Set up API access: Create a Connected App in Salesforce to enable secure API communication.
Test locally: Run the app in development mode to preview and debug your component.
Deploy the app: Build and upload the compiled app (dist folder) to your CMS or hosting service.
Connect the app: Set up app connections as needed.

CMS setup is a separate step and must be completed before deploying OmniOut content.

Other Improvements in Omnistudio: Navigate Action Element Behavior Changes

Salesforce continues to refine Omnistudio for better usability and control. One such improvement impacts the behavior of the Navigate Action element in Omniscripts, providing more precise navigation between steps.

For example, you have an Omniscript with 10 steps and insert a Navigate Action between Step 1 and Step 2 with these properties.

Page Reference Type set to Current Page
Target set to a specific step in the Omniscript using a parameter (for example, c__step=Step7)

At run time, clicking the Next button on Step 1 takes the user to Step 7. Previously, clicking Next on Step 1 took the user to Step 8.

The enhanced Navigate Action element enables flexible, nonlinear navigation paths in Omniscripts, empowering you to create smarter, user-centric flows that adapt dynamically to your users’ needs.

This update applies to Lightning Experience, Experience Cloud Sites, and Enterprise, Performance, and Unlimited Editions with Omnistudio enabled. It’s also available for customers using the standard runtime.

Sum It Up

Now you know about some of the most important Omnistudio Developer feature releases over the past year. 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?

Salesforce Platform Resources