Salesforce Summer ’23 Release Flow Top New Features

Salesforce Summer ’23 Release Flow Top New Features

1. Send Salesforce Data to an External Server Without Code via HTTP Callout (Beta)

If you can’t GET enough with HTTP Callout, now you can use the POST method to send Salesforce data to an external server in Flow Builder. Previously, only the GET method was available, which you can use to bring external data into Salesforce.

Select POST (Beta) to make a callout request that adds the resource to the external server.

Enter a sample JSON request body that the API expects when configuring the HTTP Callout, and the API infers the external data structure.

After you create the callout action, set the body for the flow by creating a resource and selecting the Apex class for the external server’s body.

After you configure the action, add an Assignment element before the HTTP Callout action element, and assign values for each of the fields on the resource.

When the flow runs, the values are set on the resource and the data is created in the external server.

2. Build Screens with Reactive Components (Beta)

Configure supported standard screen components or your custom Lightning web components to react to changes in other Flow Screen components on the same screen. Build screens that feel like single-page apps and reduce the number of screens your user needs to click through. Previously, components on the same screen couldn’t talk to each other. If you needed one component to influence another, you placed them on separate screens.

Screen Flow reactivity means your Screen Flow component updates the properties of other components on the screen based on user input. For example, you can make a Name component’s First Name field react to the Text component output.

Your existing flows start displaying reactivity when you opt into Beta and explicitly save them with API version 57.0 and later.

From Setup, on the Process Automation Settings page, select Opt into Reactive Screens Beta. Then add components to your screen, upgrade your flow to Runtime API Version 57.0, and save and run the flow as usual. The input component reacts to changes from the output component.

3. Update the Screen in Real-Time using Formulas (Beta)

Working with supported formula functions, you can configure a screen component to perform real-time formula calculations and logic. When the flow detects a change in any of the values in the formula, it recalculates and updates the value of the screen component.

For example, the user sees a real-time screen update of a price discount, tax amounts, and shipping costs. Now it isn’t necessary for users to remember what they selected on a previous screen, thus less confusion and fewer clicks.

Your existing flows only start displaying reactivity when you opt into the Beta program and explicitly save them with API version 57.0 and later.

From Setup, on the Process Automation Settings page, select Opt into Reactive Screens Beta. Then add components to your screen, upgrade your flow to Runtime API Version 57.0, and save and run the flow as usual. The input component reacts to changes from the output component.

4. Log Emails Sent with the Send Email Action

Now you can automatically log emails to a record’s Activity Timeline when using the Send Email action. You can log an email to a recipient record, which includes leads, contacts, and person accounts. You can also log an email to a non-recipient record, like an account or opportunity. Or, you can log an email to both. Previously, emails sent using the Send Email action couldn’t be automatically tracked in Activity Timelines.

5. Use Email Templates in the Send Email Action

Reuse email content with Lightning and Classic email templates in the Send Email action. If your email template has merge fields, you can use the recipient record or a related record to populate the merge fields. Or, you can use both. Previously, you couldn’t use email templates in the Send Email action.

For example, to send an email to a contact using an email template with Contact and Account object merge fields, set Email Template ID to the ID of the email template to use (1). Then, set Recipient ID to the contact record’s ID (2) and Related Record ID to the related account record’s ID (3).

6. Get Records from Data Cloud Objects in Flow Builder

Now you can use Data Cloud data in the Get Records element of a flow or in Apex code. You can view data from mapped Data Cloud objects, including data model objects, data lake objects, and calculated insight objects, but you can’t create, update, or delete Data Cloud data. For example, a customer submits a product interest form on your website. Use a flow to create a Lead record with more information in your Salesforce CRM by accessing the data in the mapped Data Cloud Form data model object using the Get Records element. Data Cloud data is available only in production orgs that are connected to Data Cloud.

Add a Get Records element to a flow. Search for the Data Cloud object that you want to use. Data Cloud objects are alphabetized with Salesforce standard and custom objects.

7. Search and Display Data Table Results in Screen Flows

Now users can search and filter their Data Table record results. The search returns the first 1,500 items. Initially, 200 records display. As you scroll through the results, additional records load progressively in groups of 100. The search results also show the number of items displayed and the total number of items found.

Add the Data Table component to a screen flow, and select Show search bar.

8. Get Field Visibility Errors during Flow Runtime

If you have field visibility errors in your flow, the flow now stops running and presents an error message. Previously, you didn’t get an error message, and the flow continued to run.

9. View More Elements on the Flow Builder Canvas

Now you can see more elements on the Flow Builder canvas with a new compact layout and a smaller Add Element button. Previously, elements were further spread out, requiring you to move the canvas more frequently to see additional elements.

To add an element using the updated Add Element button, hover over and click . Then, select an element from the element menu.

Convert More Processes to Flows with the Migrate to Flow Tool

The updated Migrate to Flow tool can help your transition to Flow Builder, and you can now use it to migrate Process Builder processes that contain scheduled actions. A scheduled action is migrated as a scheduled path in a flow. The Migrate to Flow tool takes care of all pending scheduled actions from the original process at flow runtime. After migrating a process, you can test the flow in Flow Builder. If everything works as expected, activate the flow and deactivate the process that you converted.

From Setup, in the Quick Find box, enter Migrate to Flow, and then select Migrate to Flow. Select the process that you want to convert into a flow, click Migrate to Flow, and select the criteria that you want to migrate.

10. Find Flow User Permissions More Easily

Flow user permissions are now all consolidated under a new Flow and Flow Orchestration section in App Permissions. Previously, they were dispersed throughout System Permissions.

For example, you want to add flow user permissions to a permission set. From Setup, in the Quick Find box, enter Permission Sets, and then select Permission Sets. Next, select the permission set you want to manage, and then click App Permissions. Last, select the permissions that you want to add.

11. Add Custom Information to Flow Orchestration Logs

Keep better track of orchestration progress by logging custom information for interactive and background steps. To set custom information, add a text variable named Comments that’s available for output to the step’s flow and assign a value to the variable.

In a flow called by an orchestration step, add a Comments text variable and select Available for output. You can’t use variables internal to a flow, output variables of types other than text, and other casing of Comments to add custom information to the orchestration run log.

Assign the text that you want to appear in the Orchestration Run Log to the Comments variable. You can also set the Comments variable to a flow resource—a constant, variable, text template, or formula—that contains your text when the flow runs.

When a step calls the flow in an orchestration, the string assigned to the Comments variable appears in the associated orchestration run log list and detail views.

12. Flow Integration

MuleSoft Composer for Salesforce is now Flow Integration. Flow Integration makes it easy to integrate data from any system with clicks and invoke processes in any flow. When you create a secure process to connect the information stored in different systems, you build a real-time, integrated view of your customers and business.

Additional Resources

• Salesforce Summer ’23 Release Notes

Recommended Articles

• Free Salesforce Certified Associate Exam Practice Questions
• How to Pass Salesforce Certified Associate Exam?
• Free Salesforce Admin Certification Exam Practice Questions
• Salesforce Interview Questions and Answers
• What is Salesforce Accredited Professional Credential?