Salesforce Flows
1. Action Buttons in Screen Flow
The Action Button component allows users to initiate a screen action simply by clicking a button on the screen. This action triggers an active autolaunched flow, with the results displayed on the same screen. This feature reduces the number of screens needed, enabling users to complete screen flows more efficiently and with fewer errors. Previously, users had to navigate through multiple screens to access the same functionality. Now generally available, the Action Button component comes with enhancements since the last release.
2. More Target Resource Types for Data Transformation
The Transform element now allows you to set the target resource to various data types, including Text, Numbers, Currency, Boolean, Date, and Date/Time. Previously, it only supported complex data types like Record or Apex-defined.
This enhancement makes it easier to work with both small and large datasets. For instance, if a sales manager wants to quickly assess the total value of all open opportunities for revenue forecasting, they can use Flow Builder to create a flow that retrieves these opportunities. The flow calculates the aggregated sum of the values and stores it in a number variable for later reference. It first executes the Get Records element to gather all open opportunities, then the Transform element uses this collection as its Source Data, storing the transformed value as a Number data type in the Target Data resource.
3. Disable More Screen Component Fields When Running Flow
You can now disable fields in the Action Button, Dependent Picklist, Lookup, Phone, and Slider screen components by using the Disabled attribute. When this attribute is set to true, users cannot interact with or change any fields in the component, which will display a grey background as a visual indicator.
To implement this, simply add one of these components to a Screen element in your flow and set the Disabled attribute to a Boolean resource. For example, if you have a Screen element containing a Lookup component for finding contacts, you can configure it to be accessible only when the user indicates a desire to search for existing contacts. In this case, you would set the Disabled attribute of the Lookup component to a formula that returns true when a checkbox labelled “Search Existing Contacts?” is unchecked.
4. Error Pane View
Troubleshooting flow errors has become simpler than ever. The new Errors and Warnings pane displays issues that may hinder you from saving and activating your flow, presented in a user-friendly format. This pane features links to the Flow Builder canvas, allowing you to quickly pinpoint the source of the problems. You can toggle the visibility of the pane using the Show Error button, which also includes a notification badge indicating the total number of issues that need your attention.
5. Easily Find Flow Child Resources
When referencing the child resource of an element in a flow, such as a screen component within a Screen element, you can now directly search for and select it in the updated resource menu. Previously, you needed to first select the element of the child resource before choosing the child itself. This update applies to various child resources, including Screen components, screen actions, Decision element outcomes, and Wait element configurations.
For example, if you have a screen flow that gathers a first name, last name, and email to create a contact, in the Create Records element that follows the Screen element, you can simply search for the name of your email screen component when setting the email for the new contact. After searching, you can easily select the screen component.
6. Tips to Identify Inefficient Flow Designs
New tips in Flow Builder assist you in spotting designs that may slow down your flows and raise the likelihood of hitting Apex governor limits. These tips are visible on the Flow Builder canvas and offer guidance on enhancing your flow. By implementing these recommendations, you can ensure your flows operate efficiently and mitigate potential performance problems. These tips are particularly beneficial for users who are new to flow building and may not be familiar with common pitfalls, reducing the time for troubleshooting.
7. Enhanced Create Records Element: Create or Update Records Efficiently
In Flow Builder, you can now utilise the Create Records element to create or update records based on the existence of a specified field value in the database. This enhancement simplifies and accelerates the record-saving process, eliminating the need for separate checks for existing records. By combining create and update functions into a single element, you can configure and manage the flow more easily, while also reducing the likelihood of errors from separate actions.
For example, consider a sales manager overseeing potential deals that are often updated with new information. The sales team regularly receives updates about client budgets and timelines, which need to be reflected in Salesforce. Using the Create Records element, the team can automatically determine whether to create a new record or update an existing one. To do this, add the Create Records element in Flow Builder, select Multiple for How Many Records to Create, and choose a record collection. Then, enable Update Existing Records and select the appropriate options for identifying existing records and handling any records that may fail during processing.
Sales Cloud
Account Plans for Improved Strategic Planning
Foster existing relationships and strategically expand key accounts using Account Plans. Within Salesforce, you can research and analyse accounts, establish objectives with actionable metrics, and monitor growth and development, all from a single repository. To optimise revenue potential and support your customers’ goals and challenges, use Account Plans to keep track of all your strategic planning efforts.
Examine opportunity details directly in the dashboard (1); conduct a SWOT (Strengths, Weaknesses, Opportunities, and Threats) analysis (2); identify customer needs and market dynamics (3); and set clear, measurable objectives with metrics (4). To visualise key stakeholders, check the relationship map (5).
Setup: Navigate to the new Account Plans page in Setup and enable Account Plans. Then, configure the Account Plans object in the Object Manager, add the Account Plans related list to the Account object, and optionally set up Relationship Maps.
Marketing Cloud (Account Engagement)
Locate and Merge Potential Duplicate Prospects
Maintain accurate marketing information and a clean database by merging duplicate prospects. The duplicate prospects tool, located in the Optimizer, automatically detects prospect records that share an email address, allowing you to choose which duplicates to merge. This update is applicable to all Account Engagement editions that permit multiple prospects with the same email address.
Experience Cloud
Expanded Navigation and Component Customisation
With the highly customisable Navigation Menu component, you can create a tailored navigation experience for both desktop and mobile site visitors without needing to write code. Experiment with the Site Header component (beta) to design page headers that feature your company’s logo and branding. Additionally, the Grid component now allows you to standardise cell heights for a cleaner visual layout. The Site Logo component is also now available in the component palette on all site pages, rather than being limited to just the login pages.
How: For LWR sites created using the Build Your Own or Microsite template, you can design different navigation menus and site headers for desktop and mobile screen sizes. In Experience Builder, switch between desktop and mobile view modes to customise these components. In the Navigation Menu component, adjust the Navigation Bar for desktop screens and Mobile Navigation for mobile screens. You can modify colours, borders, spacing, text styles, accent lines, and more for both sizes. A tablet in landscape orientation will display the desktop navigation, while portrait orientation will show the mobile navigation. You can add various menu items such as External URL, Menu Label, Salesforce Object, and Site Page. It is advised not to use custom CSS with this component, as it may lead to failures.
Other General Feature Update
1. Sender ID Compliance
As part of a comprehensive improvement in email security performance, Sender ID is no longer available in Email Deliverability settings. If your Salesforce org was created in Winter ’25 or later, you will not be able to enable Sender ID compliance in these settings. Technological advancements and operational efficiencies have streamlined email authentication processes, replacing the need for Sender ID functionality. This change is based on RFC7208 (Request for Comments), published in 2015.
If you are currently using Sender ID, no action is required on your part. Integrations utilising Sender ID will continue to function after Summer ’24. However, records with the v=spf2.0 prefix will not be valid moving forward, as any record beginning with this prefix cannot be used.
2. Default No-Reply Org-Wide Email Required
To meet heightened email security standards, organisations must create and verify a Default No-reply address in the Organisation-Wide Email Address settings. This verified Default No-Reply address will be used to send emails from your organisation, enhancing accountability for email deliverability. Emails may not be sent if a customer-defined Default No-Reply Organisation-Wide Email Address is not established, in order to comply with these increased security standards.
