Maintain Your OmniStudio Developer Certification for Summer ’23
Learning Objectives
After completing this unit, you’ll be able to:
- Compare Standard OmniStudio Runtime to the newly named Managed Package Runtime.
- Call a Data Mapper from Apex to run in core.
- Call an Integration Procedure from Apex to run in core.
- Enable OmniScripts to use DocuSign forms with OAuth 2.0.
- Enable continuation on FlexCards.
Salesforce 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 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 a ton of great feature enhancements over the past year. Let’s take a look at some of the more important ones for this release.
Standard OmniStudio Runtime Name Is Now Managed Package Runtime
To ensure that the purpose of the setting is clear, we’ve changed the name of the Standard OmniStudio Runtime setting to Managed Package Runtime. The setting is now enabled by default.
The change takes effect when you upgrade Salesforce and isn’t tied to an OmniStudio managed package. Your org works as it did before the name change, but the new name setting is enabled or disabled based on your org preference prior to the upgrade.
Compare the old and new names for the setting:
New Name: Managed Package Runtime | Previous Name: Standard OmniScript Runtime | Effect on Components: |
|---|---|---|
Disabled | Enabled |
|
Enabled | Disabled |
|
To view the setting, from Setup, in the Quick Find box, enter OmniStudio Settings, and then select OmniStudio Settings.
- If Standard OmniStudio Runtime was enabled when you upgraded, Managed Package Runtime is disabled.
- If Standard OmniStudio Runtime was disabled, Managed Package Runtime is enabled.
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.
Why: When Managed Package Runtime is disabled, all OmniScripts and FlexCards use standard runtime. Additionally, you can clone and update standard content and activate your content 70% faster.
Disable Managed Package Runtime for faster FlexCard and OmniScript activation and to view and modify standard OmniStudio content from the Designers. When you change the Managed Package Runtime setting, deactivate and then activate existing OmniScripts and FlexCards to change their runtime.
Because custom object-based content can’t run in standard runtime, you should first migrate all custom object data to the standard data model before you disable Managed Package Runtime. Also, ensure that the OmniStudio Designers save in the standard data model.
When Managed Package Runtime is enabled, a custom Lightning web component is generated for each OmniScript and FlexCard that you activate.
Call a Data Mapper from Apex to Run in Core
Force a Data Mapper to run in standard runtime from Apex if the Omni Interaction Configuration setting RollbackDRChanges is set to true.
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 Industries customers with a custom managed package whose orgs have an OmniStudio Permission Set License (PSL) and who have the necessary permissions to access OmniStudio standard objects.
Why: Previously, if the Omni Interaction Configuration setting RollbackDRChanges in your managed package was set to true, no existing DRGlobal Apex method could call the Data Mapper in standard runtime. The Apex method processStandardRuntime forces the Data Mapper to run in standard runtime.
How: To execute Data Mappers in standard runtime, call the Data Mapper from Apex using the DRGlobal class method processStandardRuntime.
Call an Integration Procedure from Apex to Run in Core
Force an Integration Procedure to run in standard runtime from Apex if the Omni Interaction Configuration setting RollbackIPChanges is set to true.
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 Industries customers with a custom managed package whose orgs have an OmniStudio Permission Set License (PSL) and who have the necessary permissions to access OmniStudio standard objects.
Why: Previously, if the Omni Interaction Configuration setting RollbackIPChanges in your managed package was set to true, you couldn’t run an Integration Procedure in standard runtime. To force an Integration Procedure to use the standard runtime, add useStandardRuntime = true in the API request header.
How: Specify useStandardRuntime = true in the API request header by adding it as a Remote Option on an Integration Procedure Action or directly in your Apex class.
Enable OmniScripts to Use DocuSign Forms with OAuth 2.0
OmniStudio for Vlocity no longer supports the previous method of authenticating to DocuSign. To transition to OAuth 2.0 authentication, add authentication provider credentials for DocuSign in Salesforce to create a secure connection. Configure authentication providers and add named credentials.
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 object model who upgrade to Winter ’23 (beginning with 240.11) and Spring ’23 packages.
Why: Beginning October 20, 2022, DocuSign requires new and existing REST API integrations to use OAuth 2.0 authentication. OAuth 2.0 is required for all DocuSign services.
How: To transition to OAuth 2.0 authentication, add OAuth 2.0 Named Credentials using auth provider information. Log in to your Docusign Account with the named credential. To send or sign DocuSign on behalf of another user, update the User object with the new field, DocuSignNamedCredentialSOBO.
Enable Continuation on FlexCards
Enable continuation on FlexCards that call a long-running Integration Procedure using an HTTP action or a Remote Action. You can improve performance and deliver a better user experience by enabling a continuation.
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 standard objects model and OmniStudio for Vlocity customers on the custom objects model.
Why: Use the Continuation class in Apex to make a long-running request to an external Web service.
How: From the OmniStudio FlexCards home page, open a FlexCard with an Integration Procedure data source. In the Data Source section of the Setup panel, add the key/value pair useContinuation = true in the Options Map.
Resources
- Salesforce Help: Standard OmniStudio Runtime Name Is Changing
- Salesforce Help: Disable Managed Package Runtime
- Salesforce Help: Standard OmniStudio Content and Runtime
- Salesforce Help: Call a Data Mapper from Apex to Run in Core
- Salesforce Help: Data Mapper Calls from Apex
- Salesforce Help: Call an Integration from Apex to Run in Core
- Salesforce Help: Integration Procedure Actions
- Salesforce Help: Integration Procedure Invocation from Apex
- Salesforce Help: OmniScript Supports DocuSign OAuth 2.0 Support
- Salesforce Help: Enable Continuation on FlexCards
- Salesforce Help: Continuation in Long-Running Calls