Salesforce Summer ‘24 Release: What to Expect and How to Prepare

Salesforce makes updates to its platform three times a year as part of the Winter, Spring, and Summer releases.

During this cycle, it introduces release updates. These are usually announced a few releases before they are due to be enforced and require testing to ensure your processes continue to work as designed.

Preparation

Release updates should be enabled in a sandbox first so you can test any impacts on your systems or ways of working.

If you have a developer-type skillset, you can use SFDX tools to search your Salesforce metadata for references that could be impacted by this update.

Salesforce may sometimes delay enforcement of a release update or cancel it altogether. Be sure to check the release notes for the latest changes, as things can change or shift around!

Summer ‘24

When the Summer ‘24 release is rolled out to Salesforce orgs, a number of release updates will be auto-enabled. Be sure to review the below list so you can prepare your org accordingly and review due dates against the updates in your org to allow ample time.

While we try to provide general steps you can take to enable and test these updates, the exact steps will depend on the configuration within your Salesforce org.

When planning changes in a production environment, make changes outside of working hours so they can be tested while users and clients are offline. If there are issues, this allows you to revert any changes before they impact users/clients.

Allow Only Trusted Cross-Org Redirections

What does this impact?

Any redirection that directs a user to another Salesforce org that is not currently on the “Trusted URLs for Redirects” allowlist.

How can I prepare in a sandbox?

Find any references in custom links or code that redirect a user to another Salesforce org. Add the URLs to the “Trusted URLs for Redirects” allowlist. Enable the release update and disable “Allow untrusted cross-org redirections”. Test custom configurations to ensure the redirects still work as expected.

How can I prepare in production?

Once successfully enabled and tested in a sandbox, plan the deployment of these trusted URLs and enablement of the release update in production. Beware that the Salesforce URLs are environment-specific and so these vary between environments. Be sure to thoroughly test once enabled.

Enable EmailSimple Invocable Action to Respect Organization-Wide Profile Settings

What does this impact?

If you use the EmailSimple Action in Apex, Flow, or via the REST API, you will need to prepare for this update to avoid issues.

How can I prepare in a sandbox?

Find any references to EmailSimple in Apex or Flow. Determine any instances where this action is being called via the REST API. Define when this action is called by a user and check that users have access to the organization-wide email addresses, if necessary grant access to the associated organization-wide email addresses. Enable the release update. Test custom configurations to ensure the redirects still work as expected.

How can I prepare in production?

Once successfully enabled and tested in a sandbox, plan the deployment of the organization-wide email address access changes and enablement of the release update in production. Post enablement test actions that call EmailSimple to ensure that these still work as expected.

Migrate to a Multiple-Configuration SAML Framework

What does this impact?

If this update shows up, you are using the original single sign-on framework, which will need to be upgraded to the new framework.

How can I prepare in a sandbox?

Single sign-on configuration is usually environment-specific. In a sandbox, adjust the existing configuration so that this works as expected prior to enabling the update. Follow the testing and activation steps to upgrade to the new framework in the sandbox.

After enablement in the sandbox, you may need to make some adjustments to the configuration to get this working as expected. Depending on who owns the identity system (e.g. OKTA, Google), you may need to engage with other teams internally or third parties to complete testing.

How can I prepare in production?

Work with the necessary teams to migrate the changes to your production environment, once testing is successful in a sandbox. Enable the release update and re-test your single sign-on configuration(s).

Pass the Conversation Intelligence Rule Name as Input to a Flow

What does this impact?

If you use Service Cloud Voice with Amazon Connect, Service Cloud Voice with Partner Telephony, or Service Cloud Voice with Partner Telephony from Amazon Connect.

How can I prepare in a sandbox?

Setup Service Cloud Voice in a sandbox with the conversation intelligence rules that call a Salesforce Flow. Following the test and activation steps to enable the update. Test your updated configuration to ensure flows triggered by the rules continue to work as expected.

How can I prepare in production?

Migrate any configuration changes and then follow the test and activation steps. Test your updated configuration to ensure flows triggered by the rules continue to work as expected.

Run Flows in Bot User Context

What does this impact?

Any Einstein Bot that runs a flow to perform automated actions.

How can I prepare in a sandbox?

Enable the release update in a sandbox. Thoroughly test your bots to ensure that all flows continue to work as expected without any errors. If flows error, then update the bot user so they have the necessary access to run the flow and re-test.

How can I prepare in production?

Deploy any changes to access to production. Enable the release update in production. Re-test bots to ensure they continue to work as expected and flows run without errors.

Transition to the Lightning Editor for Email Composers in Email-to-Case

What does this impact?

If you are using the docked and/or case feed email composers with email-to-case.

How can I prepare in a sandbox?

Enable the release update in the sandbox. Test the email actions against the case to ensure these still continue to work as expected via both the docked and case feed email composers. Bear in mind that to test, deliverability will need to be enabled.

Make sure you test in a controlled way so that automated email alerts don’t get sent to clients or users from the sandbox during testing.

How can I prepare in production?

Enable the release update. Test the email actions against the case to ensure these still continue to work as expected via both the docked and case feed email composers.

Summary

As a Salesforce Admin, understanding release updates and their impact on my org or business processes was always a minefield. In this guide, I attempt to make this easier for you – whether you are a Salesforce Admin, Developer, Consultant, Architect, or Business Analyst involved in this process.

If you get stuck during this process, a great place to reach out to the community for support is the Release Readiness Trailblazers community group along with any additional feature specific groups.

With each Salesforce release, new release updates are introduced, so be sure to circle back in the future for the latest updates for Winter ‘25 and beyond!

Other Resources

• Salesforce Release Notes
• Release Readiness Trailblazers
• Service Cloud – Einstein Bots
• Service Cloud
• Service Cloud Voice