A flow in Salesforce is a tool for automating intricate business procedures. In other words, it gathers data and uses the data for processes. The declarative interface used to construct individual flows is called Flow Builder. Without utilizing a programming language, one can create code-like logic with Flow Builder.
Utilize Flow Builder, OmniStudio, and Flow Orchestration to create intelligent workflows. Use Flow Integration to integrate throughout any system.
Let’s dive into the latest Salesforce Spring ’23 Flow features;
Flow Integration has replaced MuleSoft Composer for Salesforce. With Flow Integration, processes can be called in any flow, and data from any system can be integrated with a few clicks. A real-time, integrated view of your customers and business is built when a secure mechanism is developed to link the data in various systems.
Where: Enterprise, Performance, and Unlimited editions with enabled Lightning Experience offer Flow Integration for Salesforce as a paid add-on.
Using Flow Builder, Insert External Data (Beta)
Automate procedures using external data by developing Flow Builder actions that use HTTP Callout to connect to web-based service APIs. When you input the API’s specifics, Flow Builder creates a reusable action for you to utilize immediately in Flow Builder and throughout Salesforce. Establish direct integrations without using code or a middleware tool like Mulesoft.
Where: For the Enterprise, Unlimited, and Developer editions of Lightning Experience, this update is applicable.
Who: The Manage Flow and Customize Applications permissions are required for admins in order to use HTTP Callout.
NOTE: Currently in beta, this function. Customers may decide whether to test out such Beta Services at their own discretion. Any usage of the Beta Service is subject to the applicable Beta Services Terms, which are available in the Agreements and Terms.
Make Flow Orchestration Objects Shareable (Release Update)
Users no longer have access to Flow Orchestration objects when using the Manage Flow user permission after choosing to Enable Sharing for Flow Orchestration Objects. User access to Flow Orchestration objects is governed by the Manage Orchestration Runs and Work Items user permission, sharing policies, and role hierarchies. Users must still have the Run Flows user permission in order to run orchestrations and complete work items.
Where: This modification affects the Enterprise, Performance, Unlimited, and Developer editions of Lightning Experience.
When: Salesforce puts this change into effect in the summer of ’23. Go to Trust Status, look up your instance using the search bar, and then select the Maintenance tab to view your instance’s major release upgrade date.
How: To apply this update, go to Setup, type “Release Updates” in the Quick Find box, and then click on Release Updates. The testing and activation stages for Enable Sharing for Flow Orchestration Objects must be followed.
Standard OmniStudio Content is the new name for the setting formerly known as Standard OmniStudio Runtime in OmniStudio Settings. When RollbackDRChanges or RollbackIPChanges is set to true, force a DataRaptor or Integration Procedure to run in standard runtime from Apex. The flyout action container of a FlexCard should be stylish. Speed up the rendering of a long list of records on a FlexCard. For the characteristics of the FlexCard input element, use merge fields to generate dynamic values. To utilize custom labels on a Combobox in a FlexCard feature, disable the Standard OmniStudio Content setting. Replace an OmniScript modal during normal execution. On a Multi-Language OmniScript in standard runtime, custom labels are now supported in the preview.
Who: Customers of OmniStudio using the common objects model are the target audience for these release updates. The custom objects model in OmniStudio for Vlocity clients
Name Changed for a Common OmniStudio Runtime Setting
Standard OmniStudio Content is the new name for the setting formerly known as Standard OmniStudio Runtime in OmniStudio Settings.
Where: The Lightning Experience, Experience Builder websites, and all mobile app versions in the Enterprise, Performance, and Unlimited editions are all affected by this change.
Who: Customers of OmniStudio using the default objects model.
Updates to the Integration Procedures and OmniStudio DataRaptors
If the Omni Interaction Configuration setting RollbackDRChange is set to true, Apex will force a DataRaptor or an Integration Procedure to run in standard runtime.
Call a DataRaptor to Run in Core from Apex
If the Omni Interaction Configuration setting RollbackDRChange is set to true, forcing a DataRaptor to run in regular runtime from Apex is possible.
Where: All versions of the mobile app in the Enterprise, Performance, and Unlimited editions are affected by this change, as are the Lightning Experience and Experience Builder websites.
Who: Customers of Industries with a custom-managed package whose orgs have an OmniStudio Permission Set License (PSL) and who have been given the required access rights to OmniStudio standard objects
Why: No existing DRGlobal Apex method could call the DataRaptor in conventional runtime in the past if the Omni Interaction Configuration setting RollbackDRChange in your managed package was set to true. The processStandardRuntime Apex method compels the DataRaptor to operate in standard runtime.
Make the best use of these latest Salesforce Flow features with the help of our seasoned experts Apphienz. Visit our website to know more about our services and write to us at email@example.com in case of any queries.