Salesforce Summer 23 Flow Sneak Peak | All You Need to Know

The Salesforce Flow section is always full of great articles that will make the lives of Salesforce administrators much easier.  

Some new features were previously available in Process Builder but not in Salesforce Flow. This is fantastic news since it implies that Salesforce Flow is almost ready to replace Process Builder completely. The Summer ’23 update brings additional enhancements, and many of them are noteworthy! Here’s a rundown of everything coming soon’ to Flow 

POST and GET HTTP Callout Actions are now Supported

POST has a beta implementation and GET is now generally available. As you can see on the left, POST allows you to offer a sample request as well as a sample response. The graphic on the right depicts how Flow Builder attempts to estimate the appropriate kinds while also allowing you to override them. 

When you save a new HTTP Callout, it generates an External Service and a new Apex Type for both your input and output data structures. For the most part, all you need to know is that your callout will be reusable and will appear in the Action selector. 

• To make POST work in Summer ’23, you must first prepare the data that your POST action will receive. To begin, create a record variable of the suitable type manually. 
• You then populate this with data using Assign components and deliver it into the resulting Action’s sole Body input. 
• This will be smoothed out in future editions. The action will provide the inputs it supports without requiring you to establish a variable.

Don't forget to check out: Salesforce Summer '23 Release Highlights

Reactive Screens improve Formulas with Reactive Properties 

Reactive screens gain an important new feature: formulas can now be used in reactive computations. This flow screen detects input from several screen components and recalculates the monthly payment in real time. 

Use your existing Choice Sets with a new Searchable Choice Lookup Component

You can include the new Choice Lookup component in a Flow screen and give it any of the available choice sets. 

That is to say: 

• Combining it with a Record Choice Set allows you to perform a searchable lookup of any filtered set of records. 
• Combine it with a set of manual Choice resources for complete control. 
• Use it in conjunction with a Picklist Choice Set to give a searchable picklist lookup.
• Combine it with a Collection Choice Set to provide a searchable interface for any collection of records in your flow. 

The current Lookup component is still available for use in Flow screens to provide Lookup record fields. Furthermore, you may directly access Lookup fields with the Screen Element’s Dynamic Forms for Flow functionality, which allows you to choose a record variable and then drag fields onto the canvas from it. Consider the unofficial Quick Choice component for sophisticated use cases beyond these, like showing choices as rich text tiles. 

It’s worth noting that Choice Lookup with a Record Choice Set lacks some features included in the regular page layout Lookup control interface. In contrast to the standard Lookup control, which only displays a few things at a time, Choice Lookup displays the whole set of objects. 

Improvements to Data Tables 

The loading and scrolling of data tables has been improved to enable huge data sets with great performance. This has three components: 

• A table can now display 1500 rows at once, up from 200 previously. 
• You can also send a larger set of data to a data table. If you do, the first 1500 characters will be displayed alongside the entire count. 
• To make it easier to view larger sets of data, a new search bar has been added that may be used to narrow down a huge set so that everything defined by the filter is shown. 

Check out another amazing blog by SP here: Transforming Businesses with Salesforce Digital Process Automation (DPA)

Track Email Sends in Activity History

When utilizing the Send Email action, emails can be automatically logged to a record’s Activity Timeline. You can attach an email to a person record, such as a lead, contact, or person account. You can also save the email to a connected record, such as an account or an opportunity. 

Please keep in mind that logging emails with the Send Email action causes the send to use a different internal mechanism, resulting in a different daily email-sending limit. More information will be provided later. 

Email Enhancement 2: Make Use of Lightning Email Templates 

You may now add a Lightning Email Template ID to your Send Email action. If you do, the template will override the Body and Subject fields on the Send Email action. Email Templates are built around a context record known as a Related Entity Type 

When defining your Send Email action, be sure to include at least one value for the new Recipient ID and Related Record ID, in addition to the template ID. These will be utilized to populate the merging fields in the template. 

Set Email Template ID to the ID of the email template to use

• in the example below to send an email to a contact using an email template with Contact and Account object merge fields.
• Then, set Recipient ID to the ID of the contact record connected Record ID to the ID of the connected account record
• Please keep in mind that using email templates in the Send Email action modifies the API called by the action, which may have an influence on your daily email-sending limits. 

The Draught Mode is being rolled out. 

Draught Mode is now available in a few elements that use the new panel-based property editor. This includes the following in Summer ’23: 

• Background Step in Flow Orchestration Interactive Step in Flow Orchestration 
• MuleSoft’s Contribution to Flow Orchestration 
• Start Element for the Scheduled, Segment-Based Trigger Type (only available in the Starter Edition) 
• Message via Email (This is the new Data Cloud version, which is exclusively available in the Starter Edition.) 

Draft-mode enabled property editors open from the side of the screen rather than as a modal dialogue box. They do not need to be full (passing all validation) in order for the flow to be preserved, unlike dialogue boxes. This means that items might be added to a flow but then left unfinished. At the time of activation, all validation mistakes must be rectified. 

Draught Mode and panelized property editors are still being rolled out to the remaining elements. 

Try Out New Flow Features in the Starter Edition of the New Marketing Application 

The Flow team has been collaborating with the Marketing Cloud team to improve Marketing use cases by using Flow-powered journeys. Some of this will be available in the newly renamed Salesforce Starter Edition in Summer ’23 (this is the edition that was previously known as Salesforce Easy and before that Salesforce Essentials). 

• The new marketing application’s stunning array of new flow features. Many of these will be swiftly migrated to the other Salesforce editions. These characteristics are as follows: 
• New Wait Elements ‘Citizen Builder’ methods that allow a non-Admin to build flows under specified conditions. 
• Status values have been improved for tracking long-duration flows. 
• A new schedule-driven trigger for Data Cloud segments. 
• A new email action that uses Data Cloud segments and optimizes send times using AI. 

The Flow Builder Canvas is smaller and less crowded 

In Auto layout mode, icons have less white space between them. Furthermore, Add Element buttons now display as a little circle and only expand to their full size when hovered over 

A third canvas modification is that icon colors have been modified to have increased contrast to make it simpler for visually impaired trailblazers to use Flow.  This conforms to the WCAG 2.1 standard.