Maintain Your Omnistudio Developer Certification for Summer ’24

Learning Objectives

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

Recognize the name change from Omnistudio DataRaptors to Data Mappers.
Remove Organization and Profile Standard Objects from Data Mappers.
Remove Omnistudio components in unlocked packages.
Make secure HTTP outbound calls to AWS VPC.
Use automatic upgrades for managed packages.
Send documents on behalf of others.
Easily and accurately complete address fields.

Maintain Your Certification

If you hold the Omnistudio Developer credential, keep in mind that you need to complete this module by the due date to maintain your certification. Another important part of maintaining your credential is ensuring your Trailhead and Webassessor accounts are linked.

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

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 our credentials provide are our highest priority. Protecting the security and confidentiality of our exams is essential to providing our customers with credentials that are respected and industry-leading.

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

Salesforce introduced great feature enhancements over the past year. Let’s take a look at some of the more important ones.

Omnistudio DataRaptor Has a New Name

Salesforce has renamed DataRaptor to Omnistudio Data Mapper. You’ll see the updated name in the feature name and labels in the Omnistudio designers, Salesforce documentation, and Trailhead modules. Despite the name change, all APIs, object fields, signatures, and URLs with dataraptor are not changed so that your implementations continue to work as expected. The new name appears in Omnistudio Spring ’24 release and later.

Remove Organization and Profile Standard Objects from Data Mappers Used by Customer Portal Users

Salesforce customers who use the managed package runtime currently have access to Organization and Profile Standard Objects for Customer Portal users, through Data Mappers used in Omniscripts and Flexcards. Starting in Spring ’25, Customer Portal users will not be able to access these Standard Objects in Data Mappers. Salesforce recommends that our customers verify the current Data Mappers used in the Omniscripts and Flexcards that are used by Customer Portal users, and remove Organization and Profile Standard Objects from those Data Mappers. This is a proactive step to ensure that your system continues to function correctly after the Spring ’25 update.

Where: This change applies to Experience Cloud sites in Enterprise, Performance, and Unlimited editions where Omnistudio is enabled.

Who: This change impacts Omnistudio customers who use the managed package runtime.

Remove Omnistudio Components from Unlocked Packages

In Spring ’25, Salesforce stops supporting Omnistudio components in unlocked packages. Make sure that you remove Omnistudio components with unlocked packages from your deployment pipelines.

Where: This change applies to Salesforce Enterprise, Performance, and Unlimited editions where Omnistudio is enabled.

Who: This change impacts Omnistudio customers who use unlocked packages with Omnistudio components. See Metadata Coverage for the list of supported Omnistudio components.

Make Secure HTTP Outbound Calls to AWS VPC

Omnistudio Standard now supports Salesforce Private Connect for HTTP Actions in Integration Procedures. Use Private Connect to make secure outbound HTTP calls from an Omnistudio org to an external service that runs on AWS Virtual Private Cloud (VPC). In the HTTP action of an Integration Procedure, specify a named credential with an outbound network connection to AWS with Private Connect.

Where: This feature is available in Lightning Experience and Experience Cloud sites in Enterprise, Performance, and Unlimited editions where Omnistudio is enabled.

Who: This feature is available to Omnistudio customers who use the managed package or standard runtime.

Why: Salesforce Private Connect provides a fully managed secure connection between Salesforce first-party data centers and Amazon Web Services. Directly connect your Salesforce org to your Virtual Private Clouds (VPCs) that run on AWS by using Amazon’s PrivateLink. All traffic is routed over a dedicated connection (fully managed by Salesforce) without exposing your VPCs to the public internet.

Automatic Upgrades for Managed Packages

Starting in Spring ’24, we added the Omnistudio managed package to the automatic upgrade process. This process aligns with the Salesforce seasonal release cycle, where new features are delivered three times a year (Summer, Winter, and Spring). With automatic upgrades, you also get early access to upcoming releases in your sandbox preview environment.

Where: Automatic upgrades are required starting in Spring ’24.

Who: All Omnistudio managed packages.

Why: Automatic upgrades keep your sandboxes and production environments current with the latest features, let you test customizations and new features in your sandboxes, and provide regular patch updates with performance, stability, and security improvements.

If you’re looking for installation links for previous versions, contact your support team for help.

Send Documents on Behalf of Others

For integration with services such as Docusign, send on behalf of others (SOBO) allows one user to send documents for other users in an organization. This feature simplifies authentications, establishing one authenticated user instead of many. Here’s how to enable sending or signing Docusign on behalf of another user. First, Create a Send On Behalf field in the User object. Then, assign the Send on Behalf named credential from that field to the user’s page.

From Setup, in the Quick Find box, enter Users, and then select Users.
Click Edit for your Docusign user.
Under Additional Information, select the Send On Behalf field you created previously, enter the name of the Send On Behalf user named credential, and then save your changes.
Repeat these steps for each user that you want to set up to send emails or signatures as the Send On Behalf user.

Where: Lightning Experience, Experience Cloud sites, and all versions of Enterprise, Performance, and Unlimited editions where Omnistudio is enabled.

Who: Omnistudio customers who use the standard runtime: In Setup in Omnistudio Settings, the Managed Package Runtime setting is disabled.

How: When send on behalf of others is available, set up an OAuth 2.0 Named Credential to connect to Docusign. Then select a user who can send on behalf of others.

Easily and Accurately Complete Address Fields

Quickly fill out address fields in Omniscripts with Google Maps data. To enable this setting, designers add a Type Ahead block to an Omniscript and configure the Google Maps autocomplete settings, including whether to show a Google map. When a customer, agent, or other user starts typing an address, they can select an address from the matching addresses that the field shows, and the remaining address fields are automatically filled.