Skip to main content

Maintain Your OmniStudio Consultant Certification for Summer ’23

Learning Objectives

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

  • Get a better screen reader experience with accessibility improvements.
  • Utilize the latest OmniStudio FlexCard updates.
  • Follow a better migration strategy and test content in designers with OmniStudio Migration Tool updates.

Salesforce Certification

If you hold the OmniStudio Consultant 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 Consultant credential.

Note

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

Protect the Integrity of Your Certification

The quality of our certification exams and the value 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 Salesforce Help article for more details.

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

Get a Better Screen Reader Experience with Accessibility Improvements

Accessibility improvements ensure that screen readers more accurately render the OmniScript runtime experience for users.

Where: This change applies to Lightning Experience, Experience Builder sites, and all versions of the mobile app in Enterprise, Performance, and Unlimited editions where OmniStudio is enabled. This change takes effect when you upgrade Salesforce or when you upgrade your OmniStudio, Insurance, Public Sector, or Communications, Media, and Energy managed package to version 244.

How: 

Screen readers can now:

  • Navigate to read-only Lookup, Select, and Text elements.
  • Navigate to Edit Block elements that you set up in Table mode.
  • Select a value in a Typeahead element, and then tab away from the element while retaining the selected value.
  • Read asterisks to indicate required fields.
  • Read the accessible labels for ProgressBar and Tooltip Lightning web components.
  • Read the headings in Accordion Lightning web components.
  • Understand when a Block element is expanded or collapsed.
  • Open, close, and then reopen help text as needed.
  • Skip over Image elements that aren’t interactive.

Utilize the Latest OmniStudio FlexCards Updates

Now you can style the container of a FlexCard’s flyout action. Reduce the time to render a large list of records on a FlexCard. Use merge fields to create dynamic values for FlexCard input element attributes. And disable the Standard OmniStudio Content setting to use custom labels on a combobox in a FlexCard element. Here’s how.

Style a FlexCard Flyout Container

Add custom CSS to the HTML element that wraps a flyout.

How: In the Properties panel in the FlexCard Designer, add the name of a class in the Flyout Container Class property when a flyout action is selected.

Append Data to a Record on a FlexCard

Reduce the time to render a large list of records by using the Append Record action. 

How: Instead of using the Update Datasource action to update a record, which renders the whole card again, use the Append Record action to add additional data at the end of the record.

Why: When trying to render a large list of records, use the Append Record action when your record size exceeds 10 MB or is more than 140 records. This action increases your FlexCard’s performance considerably. If you use the Update Datasource action to update a large list of records, it takes a considerable amount of time to render the whole card again.

Create Dynamic Values for FlexCard Input Element Attributes

Use merge fields to create dynamic values for the min, max, minLength, maxLength, and mask attributes on FlexCard Input elements.

How: For example, to create a dynamic value for the mask attribute of a telephone element, create a custom attribute. Enter mask as the attribute name, and select a merge field (a data field variable) as its value, such as {PhoneMask}.

Disable Standard OmniStudio Content to Use Custom Labels on FlexCard Combobox

To use custom labels on a multi-select FlexCard input element whose display mode is combobox, disable the Standard OmniStudio Content setting.

How: In OmniStudio Settings, ensure Managed Package Runtime is enabled.

Follow a Better Migration Strategy and Test Content in the Designers with Migration Tool Updates

OmniStudio for Vlocity customers migrating from custom to standard objects can test standard content directly in the designers. You can migrate your content with a new, more detailed process. To enable the designers in your managed package to use the standard runtime after migration, execute anonymous Apex. 

OmniStudio Migration Tool Docs Are Updated

The OmniStudio Migration Tool documentation has more details on how to migrate your custom objects to standard objects. Learn what you must know before you migrate and how to prepare for migration. Learn the proper strategy to deploy sandboxes to assist in the migration. Learn new details about testing your standard content from the designers in sandboxes, which includes disabling the custom (package) runtime before finally pushing metadata to production.

Where: This change applies to Lightning Experience, Experience Builder sites, and all versions of the mobile app in Enterprise, Performance, and Unlimited editions.

Who: For OmniStudio customers on the custom objects model wanting to migrate to standard objects.

Test Standard Content in the Designers After Migration

After migrating your custom objects to standard objects in your sandbox, to test your standard content in the designers, your managed package must switch to using the standard data model in the designers.

Why: The OmniStudio designers can only use either the standard or custom runtime. After executing the anonymous Apex, your managed package looks for standard objects content only. Switching from the custom to standard data model disables all custom-packaged OmniStudio content in your org.

How: With the Winter ’23 or later package installed, execute the anonymous Apex in the Salesforce Developer Console of your migration sandbox org.

WARNING: Do not run the anonymous Apex in production. Run the code in your migration sandbox only. Running the code turns off the custom data model, which would break all existing custom content in your production org.

Executing the anonymous Apex adds two Omni Interaction Config records to your migration sandbox: InstalledIndustryPackage and TheFirstInstalledOmniPackage. With these records, your managed standard content can be modified in the designers.

Omni Interaction Configs after Disabling Package Runtime Migration Sandbox.

Resources

Share your Trailhead feedback over on Salesforce Help.

We'd love to hear about your experience with Trailhead - you can now access the new feedback form anytime from the Salesforce Help site.

Learn More Continue to Share Feedback