Summer24-ReleaseOverviewDeck - Stephen Stanley 27 June 2024.pdf

This slide deck is a deep dive the Salesforce latest release - Summer 24, by the famous Stephen Stanley. He has examined the release notes very carefully, and summarised them for the Wellington Salesforce user group, virtual meeting June 27 2024.

1. Summer ’24 Release
Overview


Wellington User Group
20 March 2024

Stephen Stanley
Salesforce Architect - goodcloud.team
e: [email protected]

2. Stephen Stanley
[email protected]
www.goodcloud.team

3. Admins: Clean Your
Room

4. Integration-only user clean up and new Setup
Domain
Integration-only user profile
When the integration-only user was added to Salesforce, the standard profile was far too permissive, providing full CRUD access to every
Salesforce object. In Spring ‘24 a minimum access profile was added to all orgs called Minimum Access - API Only Integrations.

Your task:
Move all your integration-only user accounts to the minimum access profile and only grant required object access using permission set(s)

Benefit
Greater security and reduced risk of data corruption caused by programming errors or misuse of user credentials

Setup Domain
Salesforce will soon be moving setup pages to a new domain *.salesforce-setup.com as part of their setup modernisation plans
Your task:
If your company controls users’ or servers’ access to the internet through firewalls or allowlists, your IT department must add
*.salesforce-setup.com to the company’s list of allowed domains. Salesforce Setup pages are now hosted on that domain.
Benefit
Continued access to Salesforce setup

5. End of Instance domain redirection
Salesforce no longer redirecting instanced URLs after 12 October 2024
To prevent service interruptions, update instanced URLs in your API calls to your My Domain login URL. Historically, instanced URLS were
forwarded within the Salesforce infrastructure to your new instance

Instanced URL:
https://ap2.salesforce.com contains the instance ap2. After your instance changes due to an org migration or an instance refresh, API traffic that
uses a URL that contains your previous instance is no longer routed to your new instance. My Domain login URLs always use the correct instance

How to find them and update them
Run the optimizer report to find them and download your org metadata into an IDE such as VS.Code and do a global substitution

Org URLs change with migrations and refreshes

6. End of Support Announced for Workflow and
Process Builder
Workflow Rules & Process Builder Support Ends 31 Dec 2025


What does this change mean for me?
If you have active Workflow Rules or Process Builder processes running
after 2025, they will no longer receive customer support or bug fixes.

Impact
After December 31, 2025, Workflow Rules and Process Builder may
continue to function and execute existing automation, but customer
support will not be available, and bugs will not be fixed.

How do I know if I’m affected
Active workflow rules
Setup | Process Automation | Workflow Rules, sort by Active column

Active Process Builder processes
Setup | Process Automation | Process Builder, sort by Status column

Free Resources
Switch to Flow Builder Learning Map
Salesforce Ben - Migrate to Salesforce Flow Course
Trailhead - Migrate Workflows and Processes to Flows

7. Salesforce Overall

8. More Actions in Intelligence Views
Quickly take action on contacts, leads and accounts
Customer Need
Previously, list view actions were not available in Contact, Lead, and
Account Intelligence Views.

Solution / How To Configure
Standard and custom quick actions from the list view appear as
buttons on the Intelligence view. You can also update multiple
records at once when inline editing.

Use Case
Send an email to an entire list of contacts; change ownership for
multiple leads; or add a label to a group of accounts. And, now you
can update multiple records to the same value inline.

Impact
Sales rep productivity
Contact, Lead and Account Intelligence Views are available in Professional Edition and above with Sales Cloud
Professional Edition
and above

9. User Access
Improvements

10. User Access Summary
Understand a User’s Access in Under 5 clicks
Customer Need
Admins have to make hundreds of clicks to determine what a user
has access to, that is changing with the Summer release. Now in
one click they can see which user permissions, object crud, FLS,
custom permissions, group & queue membership a user has!

Solution / How To Configure
Setup -> User -> select user -> View Summary button

Use Case
An admin needs to figure out which permissions a user has access
to. Instead of clicking into the profile and every perm set group and
perm set assigned to the user they can see which permissions the
user has access to in one click

Impact
Admin productivity
All Editions

11. Perm. Set/Perm. Set Group Summary
Understand what a Permission Set/Group
is granting in Under 5 clicks
Customer Need
Admins have to make hundreds of clicks to determine what a
permission set or permission set group is granting access to. Having
this summary simplifies it into under 5 clicks

Solution / How To Configure
Setup -> Permission Set or Setup -> Permission Set Group View
Summary

Use Case
An admin quickly needs to understand what a permission set is
granting access to or which permission set groups a permission set is
used in or which permission sets are granting access in a permission
set group. An admin can now in one click see a quick summary of
what is in a permission set

Impact
Admin productivity
All Editions

12. Public Group Summary
Understand where a public group is used in under 5 clicks!
Customer Need
Public groups can be used across the platform but there isn’t an easy
way for an admin to understand when they add a user to a public
group what they are actually getting access to. Now with the public
group summary they can see the most used places for public groups
in under 5 clicks!

Solution / How To Configure
Setup -> Public Groups -> View Summary

Use Case
An admin needs to understand where a public group is used. They
will be able to see which sharing rules, report and dashboard folders
and list views.

Impact
Admin productivity
All Editions

13. More Granular Access for Managing Users
Introducing new Permissions :
‘Freeze Users’ / ‘Monitor Login History’
Customer Need
Customers need granular control over user permissions. 'Freeze User' and
'Monitor Login History' perms are currently tied to 'Manage Users' perm, leading
to excessive access on User records. There's a need to separate these permissions
for role-appropriate access.

Solution / How To Configure
We introduce "Monitor Login History" and "Freeze Users" perms. "Monitor Login
History" grants access to user login data, while "Freeze Users" allows user
freeze/Unfreeze access. Both can be assigned independent of ‘Manage Users’
perm and are auto-enabled with it.

Use Case
An Admin can assign these permissions to a User through a Permission Set.
"Freeze Users" grants the ability to freeze/unfreeze other users' accounts;
"Monitor Login History" grants access to view user login history via user detail
page, setup and, using report permissions, generate reports on this data.

Impact
Improved User access control, Security and Compliance
All Editions

14. User Access Policies
Automate and Migrate User Access with User Access Policies (Generally
Available)
Customer Need
Simply the new user provisioning process and assign permissions, queues,
groups, package licenses and permission set licenses based on user attributes.
With user access policies, you define aggregated access for your users in a
single operation. You can create policies that grant or remove access whenever
users are created or updated, or in a one-time manual migration.

Solution / How To Configure
From Setup | User Management Settings, enable User Access Policies
Navigate to Setup | User Access Policies and create your own grant or revoke
policies

Use Case
As a System Administrator, I need to ensure that user access is done
consistently and easily

Impact
Fewer wrongly assigned permissions and licenses, reduced permission and
license accumulation. Reduced administration effort

15. Admin Features

16. Schedule Apex jobs using a cron expression
Allows jobs to run more frequently than daily



Customer Need
Companies need an easy way schedule jobs to run more than once per
day, per week or at times other than on the hour. You can also pause
and resume jobs from this page

Solution / How To Configure
From Setup | APEX Classes or Setup | Scheduled Jobs, click [Schedule
APEX], then select the cron Expression radio button and enter a cron
expression.

Use Case
As a System Administrator, I need to be able to run jobs at particular
times or on a particular recurring schedule

Impact
Allows jobs to be run closer together or more frequently than daily

Useful resource:
Build cron expressions or see when a given cron expression will run next
www.cronmaker.com

17. Field History Tracking and Field Audit Trail
New enhancements to FHT and FAT


Customer Need
Companies need an easier way to establish data retention and change
tracking for Salesforce objects.

Solution / How To Configure
Enter the new Field History Tracking user interface in Setup. You can
now easily toggle the tracking status of any field for every object in a
single page.

Use Case
As a System Administrator or an Auditor, I need to track change history
on all key user-entered or integration-entered data fields with fewer
clicks

Impact
Boost admin productivity by setting up Field History Tracking in seconds.

18. Limit Who Receives Notifications About Certificate
Expiration
Reduce the noise caused by certificate expiry
Customer Need
Control who is notified when certificates are close to expiry or are expiring

Solution / How To Configure
Add the Receive Certificate Expiration Notifications to a new permission set. Then assign that permission set to a user. Users with the
permission receive emails at 60, 30, and 10 days before a certificate expires.
To prevent service interruptions caused by expired certificates, all admins are emailed the day before and on the day of a certificate's
expiration.

Use Case
As a System Administrator who has nothing to do with certificates, I don’t want to be troubled by emails I can do nothing with

Impact
When you assign the new system permission to at least one admin, all other admins see fewer certificate-related emails in their
inboxes. And admins that you designate to receive expiration notifications are better informed about how to handle impending
certificate expirations.

19. Dynamic Forms and Actions on Mobile
Dynamic Forms and Actions are now available on Mobile
Customer Need
This feature allows admins to use drag-and-drop tools in Lightning App
Builder to optimize the field-level visibility rules on records. Dynamic
Forms improves page load-time performance and simplifies the
end-user UI.

Solution / How To Configure
Same as desktop experience.

Use Case
Certain Sales Reps should see more fields than their counterparts in the
same profile.

Impact
Less admin time to configure pages for mobile.

20. General Flow
Enhancements
These enhancements are available for
all flows, or at least most of them!

21. Automation App
A new way for Admins and Marketers to access
Flow Builder and related tools
Customer Need
Customers have needed a way to manage Flows more efficiently, with features
such as search, categorization, and availability outside of setup.

Solution / How To Configure
The Automation Lightning App will be easily accessible from Lightning App
Launcher. Just click on the app launcher, search for Automation, and you can
navigate to the app.

Use Case
As a long-time Flow Admin, I haven’t been able to search for Flows and organize
them in a customizable manner. With the Flow Lightning App, we have a new
lightning list view that includes searching for Flows. We’ve also added custom
category and subcategory fields that can be used to classify Flows by any
taxonomy relevant to the customer. Additionally, the app includes a Home page
that can be customized by Admins to further tailor the Flow management
experience for all users in their organization.

Impact
Better organization and management of Flows outside of Setup!

22. Flow Builder Loading Speedup
Global Variable Loading
Customer Need
Loading the list of available global variables in Flow Builder
can take a considerable amount of time, particularly in orgs
with large numbers of variables, typically Custom Labels. The
result is a less-than-delightful experience when editing flows.

Solution / How To Configure
Automatically enabled performance optimizations
dramatically reduce the time it takes to load the list of
available global variables in Flow Builder.

Use Case
Selecting variables in property editors while building flows in
Flow Builder

Impact
Faster loading of global variables in Flow Builder
Happier Flownatics! *Graph depicts impact in a sample test org with 100,000
global variables. Note the logarithmic scale on the Y axis!

23. Label-First Toolbox and Simplified Panel
Customer Need
Users want a streamlined way to name elements and find them in the toolbox

Solution / How To Configure
From the canvas in Auto-Layout mode, add an element to your flow. The Label
and API Name values are auto-generated with unique values and the label is
selected so that you can seamlessly edit.

Click Toolbox and scroll down to view your element, listed by label. Hover over
the tooltip icon to see the element’s API name and label.

Use Case
Element panel headers are now simplified and more consistent when adding &
editing an element. Elements are listed in a more friendly way in the toolbox.

Impact
Seamless element naming

24. Schedule-Triggered Flow Debug
Select a record, skip conditions, and see total number affected
Customer Need
Users need to test multiple records when building and debugging
scheduled flows.

Solution / How To Configure
In schedule-triggered flows with batches configured in start node,
the user will see a new record selection option when pressing Debug.
Once debug runs, they will see an additional card letting them know
the total number of affected records.

Use Case
When an admin builds a flow, they can quickly test it on different
records. They can also evaluate overall impact of the scheduled-flow
in environments without activating or running into limits.

Impact
Improved debug and testing for admins using schedule-triggered
flows

25. Schedule-Triggered Flow:
Async Governor Limits
Customer Need
Schedule-triggered flows previously used synchronous governor limits for their transactions.
This was limiting to customers who had larger, more complex processes to automate.

Solution / How To Configure
Schedule-triggered flows (API Version 61+) will now be run with asynchronous governor
limits.
To apply these changes to existing flows, customers will need to update their
schedule-triggered flows to the latest Flow API version. Newly created schedule-triggered
flows will automatically be created on an applicable version.

Important note: We expect this to be useful for calling things like invocable actions and
callouts. However, we still recommend customer exercise caution when combining any large
DML operations within a schedule-triggered flow that are also configured to run on a batch of
records.

Impact
More processing can take place in a single scheduled flow run.

26. isBlank & isEmpty
Configure Conditions More Easily with Is Blank and
Is Empty Operators in Flows
Customer Need
Customers have been frustrated with the inconsistency of how isNull behaves in Flow.

Use Case
1.isBlank - After user entered their info into a form, I want to make sure Zip Code is
not blank.
2.isEmpty - After getting recent cases for a particular account, I want to
make sure there are at least 1 case in the collection before going down
a path in Flow.

Solution / How To Configure
Instead of using isNull, use isBlank just like the guidance for Formula and Apex. This
will check for both null and blank values together. As for collections, you can use the
new isEmpty operator to check whether a collection has items in it. Previously, you
needed to create a number field and use that to count the number of items.

Impact
Much more consistent across all data types and does not need multiple steps to check
for empty collection.

27. Screen Flows

28. Customer Need
When you need to collect one or more sets of data, you may not know how many the end user
will need to add. Previously, the only way to accomplish this was to manually reroute the user
back to the same screen over and over again or to build a single-use component (full code).

Use Cases
●Add work & education history to job application
●Add vehicles & drivers to insurance policy

Solution / How To Configure
1.Add a Repeater component to your screen.
2.Drag other components into the repeater and configure them.
3.Add a Loop to your flow to map the resulting collection data into the right data structure,
such as a CRM object or Apex-define type for external services.
4.Use Create Records or an external callout to commit the data you collected in the
Repeater component.

Impact
Keep your users on the same screen while collecting multiple records, instead of rerouting the
user back to the same screen over and over again, thereby increasing user efficiency.
Repeaters
Enable users to create lists of data at runtime

29. Customer Need
Flow builders need a way to enforce business logic to funnel users through completion of a
form and to summarize information entered by a user that resembles an input field.

Use Cases
Disabled
●Disable inputs until a user provides key information on the screen, like a Terms
Agreement or Lookup to a related record
Read Only
●Summarize information a user entered on a previous step or elsewhere on the screen

Solution / How To Configure
●Set the ‘Disabled’ or ‘Read-Only’ inputs for the newly supported components to
$GlobalConstant.True / $GlobalConstant.False or use a boolean formula resource to set
them reactively

Impact
Admins can prevent users from editing fields and better enforce business logic
Restrict or allow input in your components
based on business logic
Conditionally Disabled and
Read-Only Input States
Read Only Example
Using conditionally disabled fields to prefill and
lock options in a case screen flow

30. Customer Need
Flow builders need to be able to update address fields using a state’s StateCode
and country’s CountryCode. By not using these, users could see system errors.

Use Cases
When you need to update or create a State or Country on a record when the
‘State and Country Picklists’ feature is enabled

Solution / How To Configure
1.Ensure the org has the ‘State and Country Picklist’ feature enabled
2.When updating or creating a record with an address field, use the Country
Code and State or Province Code outputs instead of the
Country Value and State Value outputs

Impact
Flow builders can now use the Address component when their org has
State/Country Picklists enabled
State and Country Picklist Support Added
Address Component Enhancements

31. Fill in addresses faster with Google address lookup
Address Component Enhancements
Customer Need
Filling out addresses can be slow and tedious. Instead of a user going
field by field to complete an address, they would prefer to just search
for the address and have it autocomplete all of the fields for them.

Solution / How To Configure
1.In the Enable Google Maps Search Field field in the
component, enter {!$GlobalConstant.True}. Specify a label for
the search field. Save and run the flow.

Considerations
Google lookup is not supported in Playground, Experience Builder
sites, Lightning Out, Lightning Components for Visualforce, and
standalone apps. While it may work, these environments are not
officially supported.

Impact
End users can now complete addresses much more quickly

32. Run autolaunched flows within your screen
for more dynamic screen flows
Keep users on the same screen
with Action Buttons (Beta)
Customer Need
Flow builders need to retrieve data based on user inputs to keep them on the same screen. Action
Buttons with screen actions will prevent context switching and enable faster form completion, reduces
mistakes, and unlock a whole set of new use cases for screen flows.

Use Cases
●Perform a callout from a button that takes an Address, Quantity, and Weight and returns an
estimated shipping cost back into the screen
●After selecting a Price Book, retrieve the associated products and price book entries to display to
the user in a single screen

Solution / How To Configure
See following slides
Design your screen > Create/re-use an active autolaunched flow > Add your
Action Button to the screen > Use the action’s results in other components

Impact
Flow builders can now build even more dynamic screens by querying data
and executing complex logic on a single screen.
Considerations / Notes
•Ensure your flow is API 59+
•Avoid using Wait elements if you need
the results in the same screen
•An in-depth walkthrough of the feature will be
available on admin.salesforce.com in May ‘24.

33. Collection choice sets are now reactive and respond to changes
Generate Dynamic Choice Options
Customer Need
Customers want to stay on the same screen when completing their screen
flows. Choice components today have choice options that cannot be
changed in the same screen until now.

Use Cases
●Select an account and generate a set of contacts in a radio button,
choice lookup, or multi-select component to keep users on the same
screen
●Generate a set of shipping options and prices based on data the user
entered on the same screen

Solution / How To Configure
1.Begin with a component that outputs a record collection as an output
2.Define a Collection Choice Set resource whose collection is the
output of that component
3.Use the collection choice set as a choice option for Choice Lookup,
Radio, Picklist, Checkbox Group, Multi-select Picklist component.

Impact
Flow builders can now enable users to make choices that are dynamically
generated on the same screen to reduce decision fatigue of bouncing
between screens.
Considerations
•Ensure your flow is API 59+
•If a default value is set for a choice and that value
doesn’t exist in the collection when the screen
loads, it will not be selected when the data is
loaded from an action button or same-screen LWC.

34. Integrations & Actions

35. Actions and Subflow Panels
Find and Configure Invocable Actions and Subflows
Customer Need
As the number of invocable actions and subflows in an org grows,
finding the right one to add to a flow becomes more difficult.
Customers need to be able to see all of the available information about
actions and subflows, including API names and descriptions.

Solution / How To Configure
The new Actions and Subflows panels provide enhanced search that
searches all available metadata (label, API name, and description).
Panels display the relevant API names and descriptions.

Use Case
Finding, selecting, and configuring invocable actions
Finding, selecting, and configuring subflows

Impact
Improved search makes it easier to find the right action or subflow.
Descriptions are now available during search and configuration. API
names are now shown, including Apex class names for Apex actions.

36. Invocable Action Input Constraints
Add default values & placeholder text to action inputs
Customer Need
Users want to make Invocable Action (IA) inputs more descriptive for consumers
like Copilot and Flow.

Solution / How To Configure
IA inputs can now have default values and custom placeholder text added to the
invocable variable annotation in both Java and Apex actions. Existing action may
not display these attributes since they must first be added by action
owners/developers.

Use Case
Default values & placeholder text are descriptive input attributes that provide
greater transparency and guidance to action consumers and end users. Default
values describe which value(s) the system will use if users do not provide one.
Placeholder text often provides examples of valid values a user can enter.

Impact
Actions can be used more accurately and powerfully by consumers and admins.
This is how default values & placeholder text
are surfaced in the Flow Actions panel UI.

37. Lock a Record
Use a Flow to lock or unlock a record!
Customer Need
Before Summer ‘24, the only way to lock a Salesforce record was to use
APEX or create an Approval Process for that object. Customers can use
the power of flow with a new invocable action to lock or unlock a record.

Solution / How To Configure
Add the “Lock Record” action to your flow from the list of actions.
Configure it with the target record and the action you want to apply
“Lock” or “Unlock”. Additionally, you can pass an a group or queue ID of
users who are allowed to update the record while it is locked.

Use Case
As a Salesforce Admin, I want to lock a record while it is being reviewed
by a given user.

Impact
Additional capability for Flow that was only available through code.

38. Data Transform Mapping Tips
Guided Experience and Show Error in Context
Customer Need
It’s hard to get started with mapping and transforming complex nested
data structures. There are lots of mapping validation and scoping rules
where you can or cannot map to certain fields and collections.

Solution / How To Configure
Mapping tips give you a guided experience when doing the mapping and
show you in-context errors when you are doing something wrong. This way,
users do not have to read error messages from the top of the flow and try
to figure out what they are doing wrong just from the text.

Use Case
For example, when mapping a field from a collection, you can only map to
the same collection once a mapping is set. A less technical person might
not understand why the Transform Element is not letting you map, but with
in-context mapping tips, it’ll explain the reason right next to the field.

Impact
Much easier to use!

39. Check for Duplicates Before Creating Records in a
Flow
Prevent unhandled exceptions caused by “Select one of these?” prompt
Customer Need
Proactively handle scenarios where potential duplicates exist

Solution / How To Configure
In Flow Builder, create a flow that includes a Create Records element. In
the Create Records pane, enable Check for Matching Records. Add one or
more conditions. Select whether to update or skip matching records. Save
the flow.

Use Case
To prevent duplicate records, check for records that match a set of criteria
in the Create Records element. Choose to skip matching records or choose
to update matching records with the values that you provide.

Impact
Fewer flow failures caused by duplicate rule alerts and prevention
configurations

40. Thank you
Contact me: [email protected]
www.goodcloud.team
Salesforce Architecture Guidance
Partner Quality Management
Integration Development
Non-Profit Success Pack Guidance
Salesforce Flow Design/Development
Lightning Component Development

Anything where you need a second opinion