With three major releases each year – Winter, Spring, and Summer – the Salesforce platform is always evolving, and we know we all have to keep up with that.
Sandbox testing is crucial: Using a dedicated sandbox for the Summer '24 Release allows for comprehensive testing of new features, mitigating risks before deployment.
SFDX tools streamline changes: Utilizing Salesforce DX tools and version control enhances the management and deployment of updates, ensuring smoother transitions.
Security enhancements: The new update restricting cross-org redirections to trusted Salesforce orgs strengthens security and reduces phishing risks.
As we gear up for the Summer ’24 Release, we (Salesforce users) must stay informed about what's on the horizon. This article will look at what you can expect from the upcoming Summer ’24 Release.
From new features to essential updates, I'll explain everything to help you prepare for the changes ahead. Whether you're a seasoned Salesforce professional or just getting started, this guide will provide valuable insights into what you can expect from the Salesforce Summer ‘24 Release.
What's coming in the Salesforce Summer ’24 Release?
April 16 – Get ready for the release: Starting April 16, we saw informative blog posts introducing the upcoming Summer '24 features. These blog posts covered Flow enhancements, user access changes, and other improvements.
April 18 – Early access registration: From April 18, you could sign up for early access to explore the new features in a Developer Edition environment. This exclusive opportunity lets you try out the upcoming functionalities firsthand.
April 24 – Release notes publication: The detailed notes provide crucial information about the changes and new features coming your way, so be sure to review them carefully.
May 9 – Sandbox refresh deadline: Remember to refresh your sandbox by May 9 to test how the new features will work with your custom setups. This is essential for identifying and addressing any issues before the updates go live.
May 10 – Sandbox preview begins: Starting May 10, take advantage of the sandbox preview period to test the new features without affecting your operational environment. This is your chance to get hands-on experience with the upcoming changes.
May 17, June 7, and June 14 – Main release rollouts: These dates mark the main release rollouts, when the new features will be deployed across Salesforce instances. Check the maintenance calendar to know when your instance will be updated.
May 29-31 – Live release preparedness: Join live demonstrations and discussions with product managers from May 29 to May 31. This will help you better understand the key features and prepare for the changes ahead.
Preparation for the Summer '24 Release
Getting ready for a Salesforce Release is really important to keep things running smoothly for your organization. Here's why it matters and what you can do to get prepared:
Why preparation is important
When Salesforce releases updates, they bring in new features and changes. If you're not ready for them, it can cause problems like downtime or things not working as they should.
By preparing in advance, you can ensure that your Salesforce system continues to work well and meets your business needs.
Testing in a sandbox
Ideally, release updates must be enabled in your sandbox.
Sandbox testing is a safe way to try out new features without affecting your live system. You can experiment without worrying about breaking anything.
Create a special sandbox just for testing the Summer '24 Release. This lets you see how the changes will work in your real system.
Try out different scenarios and ask your team for feedback. This helps catch any problems early on so you can fix them before going live.
Using SFDX tools for Developers
Salesforce DX (SFDX) tools are great for you if you're a Developer. They help manage changes and ensure everything goes smoothly when updating your system.
Use SFDX commands to retrieve and deploy changes in a controlled way. This keeps things organized and reduces the chance of mistakes.
Keep track of changes using version control, like Git. This makes it easier to roll back changes if something goes wrong.
The Summer '24 Release packs a punch with a lineup of significant updates to enhance the Salesforce platform. Let's dive into what's coming your way.
Auto-enabled release updates overview
Every Salesforce Release comes with automatic updates that roll out across all orgs. These updates are like little boosts, bringing improvements in security, usability, and functionality. They're hassle-free, saving Admins the trouble of manually activating them. But it's still essential to understand what changes are coming down the pipeline.
⏰
Author's note: In this blog, I offer a basic framework for rolling out and testing updates. The exact steps will depend on how your Salesforce setup is configured. When making changes in a live environment, it's best to do so during after-hours to minimize disruption to users and clients.
List of specific updates and their impact
Let's delve into the significant updates arriving with the Summer '24 Release.
Allow only trusted cross-org redirections
Impact: With this update, Salesforce aims to strengthen security measures by limiting redirections exclusively to trusted Salesforce orgs. This ensures that users are directed only to verified destinations, reducing the risk of unauthorized access or phishing attempts.
How to prepare: In the sandbox environment, Administrators should first identify and whitelist URLs for testing purposes. They can then simulate redirection scenarios to ensure that the necessary adjustments are made to custom links or codes. Once validated in the sandbox, Administrators can plan the deployment of these changes to production. Thoroughly test in production to ensure that the redirects function as expected without impacting user experience.
Enable "EmailSimple" invocable action to respect organization-wide profile settings
Impact: The "EmailSimple" invocable action, utilized in Apex, Flow, or via the REST API, is essential for email-related functionalities within Salesforce. This update ensures the action aligns seamlessly with organization-wide email settings, maintaining consistency and compliance across communication channels.
How to prepare: In the sandbox, review all instances where the "EmailSimple" action is used, be it Apex, Flow, or called via REST API. Determine when a user calls the action and adjust user access configurations as necessary to respect organization-wide email settings. Once you enable the update, conduct rigorous testing to validate functionality and ensure compliance. Once validated in the sandbox, you can deploy the changes to production. Post-deployment testing in the production environment must confirm that the "EmailSimple" action behaves as expected and adheres to organization-wide profile settings.
Migrate to a multiple-configuration SAML framework
Impact: The transition from the old single sign-on framework to the new multiple-configuration SAML framework represents a significant update in Salesforce's authentication mechanisms.
How to prepare: Sandbox preparation involves adjusting configurations to align with the new SAML framework specifications and conducting thorough testing to validate compatibility and functionality. Collaboration with relevant teams is vital to ensure comprehensive testing. Once this update is enabled in your sandbox, you'll have to adjust some configurations to make it work as expected. Moreover, once validated in the sandbox, you can plan to deploy these changes to production. Meticulous planning and execution are necessary to minimize disruption to users' access. Once done, test your single sign-on configuration again.
Pass the conversation intelligence rule name as an input to a Flow
Impact: If you're using Service Cloud Voice with specific telephony setups, this update streamlines the integration process by enabling the seamless passing of conversation intelligence rule names into Flows. This enhancement facilitates more efficient workflow automation and ensures the seamless execution of predefined actions based on conversation insights.
How to prepare: In the sandbox environment, Administrators must set up Service Cloud Voice and configure conversation intelligence rules to pass names as input to Flows. They must also conduct thorough testing to validate the integration's functionality and identify potential issues. Configuration adjustments may be necessary to align with updated requirements. Once validated in the sandbox, you can deploy the changes to production and test the new configuration, ensuring your Flows triggered by new rules work as expected.
Run Flows in bot user context
⬇️
Author's note: Do you want to know my recommendations for Salesforce Flow best practices? Have a look at the infographic below.
Impact: With the rapid increase of Einstein Bots facilitating automated interactions, ensuring Flows run within the designated bot user context has become necessary for maintaining operational efficiency and compliance. This Release ensures seamless execution of automated actions within the defined context, enhancing the overall user experience and operational effectiveness.
How to prepare: First, enable the release update in your sandbox and conduct comprehensive bot testing to ensure Flows runs within the designated bot user context. You'll then identify and address any potential issues before deployment to minimize disruptions. Once validated in the sandbox, Administrators can proceed with deploying the changes to production. Thorough testing in the production environment is necessary to confirm that bots function as expected and Flows run without errors.
Transition to the Lightning Editor for email composers in "email-to-case"
Impact: Transitioning to the Lightning Editor for "email-to-case" functionalities represents a significant advancement in email composition within Salesforce. This update offers users a more intuitive and feature-rich email editing experience, enhancing productivity and user satisfaction.
How to prepare: Activate the release update within the sandbox. Using both docked and case feed email composers, check if email actions still work well with cases. Remember to turn on deliverability for testing. You will then ensure testing is controlled to avoid sending automated email alerts to clients or users from the sandbox. Once done with the sandbox, deploy changes to production. Turn on the release update and test email actions with cases to confirm smooth operation across docked and case feed email composers.
Scratch Org Snapshots
Scratch Org Snapshots are set to revolutionize the way Developers work with Salesforce environments, and with the Summer '24 Release, they will be generally available (GA).
Impact: Scratch Org Snapshots allow you to capture and restore the state of your scratch org, including metadata, data, and settings. This means you can now create snapshots of your work at different stages of development and easily revert back to them if needed.
How to prepare: In the sandbox environment, familiarize yourself with creating and restoring Scratch Org Snapshots. Experiment with different scenarios to understand how they can benefit your development workflow. Consider implementing Scratch Org Snapshots into your development process. This might involve updating your existing workflows and procedures to incorporate the use of snapshots. Once you're comfortable with the concept and implementation of Scratch Org Snapshots in the sandbox, you can start planning for their deployment in the production environment.
Remember to communicate any changes to your development team and provide user training if necessary.
If I had to sum up Summer '24 in four steps, I'd say:
Explore the pre-release org: Start by enrolling in a pre-release Developer Edition environment. This dedicated space is equipped with upcoming features that enable you to explore and grasp new functionalities without affecting your live setup.
Sandbox preparation: Refer to the Salesforce Sandbox Preview Guide to strategize your updates. Decide whether to stick with the non-preview instance or transition to a preview instance before the sandbox preview commences on May 10. Ensure to refresh your sandbox by May 9 to incorporate all requisite features for testing.
Testing new features: Use the sandbox environment to test new features thoroughly. Evaluate their compatibility with your existing customizations and workflows. In a nutshell, utilize this opportunity to identify and resolve potential issues well in advance.
Final checks before rollout: As your Salesforce instance nears its upgrade window on May 17, June 7, or June 14, perform comprehensive final checks. Ensure that all systems and processes integrate seamlessly with the new release, minimizing disruptions.
Be release ready
In conclusion, the Salesforce Summer '24 Release brings exciting updates to enhance platform functionality. Whether you're a Salesforce Admin, Developer, or Consultant, I've tried to make this short guide as easy as possible.
If you still need help, use community resources for support and collaboration, such as:
Sushrut is a skilled Salesforce Developer, Technical Writer, and Entrepreneur. His expertise includes front-end dev, Web3, and DevRel. He leverages technology to craft exceptional digital experiences.
