Table of Contents
Every year, Salesforce comes out with multiple upgrades for the entire platform. After the successful launch of the Winter ’25 release, it is now almost time for the Salesforce Spring ’25 Release. It is set to be released in the coming February 2025 with new features and upgrades for Sales Cloud, Service Cloud, Marketing Cloud, Data Cloud, and many more.
When the new release comes out, all the updates will be auto-enabled in your system. But before that, you must make sure that your Salesforce org is ready to take on the new release. Both your sandbox and production environment will need a deep cleanse and preparation ahead of time. This would allow you to test the changes and review the data before the release date.
So, while waiting for the Salesforce Spring ’25 Release Notes, check out this guide on how you can prepare your org for the updates.
1. Change Einstein Activity Capture Permissions for Sales Engagement Basic Users
If your org has Sales Engagement Basic User permission set in place and allows access to Einstein Activity Capture, then you will need to change the permission settings for this feature. To ensure the correct level of access to users, you need to review the Sales Engagement Basic User permission set.
Prepare in Sandbox
Use the following steps to change permission sets of users in a sandbox:
- No Code – Create a Permission Set List View that shows permission sets with Use Einstein Activity Capture
- Pro Code – Search in Permission Set Metadata for reference to AutomaticActivityCapture
If the users do not need Sales Engagement Basic User permission set for the other permissions, then you may remove it.
Prepare in Production
Use the same steps as taken in Sandbox to adjust permissions in production. As a last step, check if the Einstein Activity Capture is working fine.
2. Enable ICU Locale Formats
This refers to the format of date, time, user names, numbers, etc. To make the format easier in the new release, the Salesforce setup will use ICU locale formats instead of Oracle’s Java Development Kit.
Prepare in Sandbox
You might already be using the ICU Locale Formats. To check, see if Enable ICU formats for en_CA locale are enabled. If it is not enabled, then turn it on and test how it affects your existing processes.
Prepare in Production
You can directly deploy the changes from the sandbox to the production once you are satisfied with the implementation and processes are executed as required.
3. Enable LWC Stacked Modals
We know the previously done migration of internal components from Aura to LWC. With the upcoming release, the UI must be changed to keep it intact if you use Custom Actions.
Prepare in Sandbox
In a low-code Salesforce setup, you need to review what custom actions are available, whether they are Aura or LWC. In pro code, you will need to run the following query for review:
| SELECT id, DeveloperName, EntityDefinition.DeveloperName, Label, ManageableState, MasterLabel, Type FROM QuickActionDefinition where type = ‘LightningComponent’ or type = ‘LightningWebComponent’ |
It is better to note down the current navigation and compare it to the expected behaviour after saving the new update.
Prepare in Production
If you want the users to see the new UI, deploy the changes directly from the sandbox and test each component.
4. Enable Secure Redirection for Flows
With the new release, the retURL parameter will likely stop the redirection of flow. The URL must be listed on the Trusted URLs for Redirects in the Salesforce setup for continued functioning.
Prepare in Sandbox
To prepare for safe redirects in the sandbox, you need to check your custom actions. Test and add the URLs to the Trusted URLs list. Additionally, in pro code, you need to search through your Salesforce metadata for retURL. Once you find the target URL, add it to the list.
Prepare in Production
Deploy the Trusted URLs for redirects in production safely and run tests to check the functionality.
5. Enforce Permission Requirements Defined on Built-In Apex Classes Used as Inputs
The context in which you use the built-in Apex class to call a flow or process builder will change. This requires you to optimize the methods that run Invocable Apex.
Prepare in Sandbox
You first need to identify all your Invocable Apex Methods and then test them. Don’t forget to test the methods that can be called via REST API. Here’s how you can do it:
- No code – Search Apex for @InvocableMethod
Review Flow, Process Builders, Apex, or Einstein* Features for references.
- Pro code – Search Apex Metadata for @InvocableMethod
Once you’ve found any matching references, search Flow, Process Builders, Apex, or Einstein* Metadata for those references
Prepare in Production
Once these changes are made in Sandbox, you can safely implement them in other environments, including production.
6. Enforce Rollbacks for Apex Action Exceptions in REST API
Right now, REST API is used to call any Apex Action. But with the new release, this is about to change.
Prepare in Sandbox
Usually, the REST API is initiated by an external system, so it is best to use a tool like Workbench to test and run APEX after the release. For now, you can search for Invocable Method in Apex and Apex Metadata to identify any trigger.
Prepare in Production
After the successful test run, you need to deploy the changes to your production environment and check if everything works as expected.
7. Sort Apex Batch Action Results by Request Order
The order in which we currently see the results after running an Apex Batch Job is about to change. The results will now be shown in the order of requests received.
Prepare in Sandbox
You can type BatchApex to view Apex Jobs from the setup itself. Follow it up with a test run to ensure smooth results.
Prepare in Production
Try to deploy the changes from sandbox to production outside of working hours. This would help in avoiding any impact on users. Rerun tests to make sure that the Apex Batch job works as expected.
8. Use an Apex-Defined Variable for All Intelligence Signal Types
The Salesforce Spring’25 Release aims to modify the Signal types. You need to set intelligence signals as input for Autolaunched Flows and Recommendation Strategy Flows. Otherwise, there would be an error in communicating signals between Service Cloud Voice and Amazon Connect, Service Cloud Voice with Partner Telephony from Amazon Connect, or Service Cloud Voice with Partner Telephony.
Prepare in Sandbox
First, review whether your Conversation Intelligence rules are set up with Service Cloud Voice or not. If yes, then adjust the flows that receive Apex-defined variables and run the test after the update.
Prepare in Production
Once the flows are updated in the sandbox, deploy them to the production environment and rerun any tests to ensure intelligence rules are still triggered as expected.
9. Verify Your Return Email Address for Sender Verification
It is proposed in the new update that after Spring 2025, Salesforce will require verification of any return address before they can be used. This would enhance the security of contact information.
Prepare in Sandbox
Every user will have to visit their settings and manually verify their email address. It is an easy process as you only need to request a verification, and you will receive a link in your inbox with further instructions.
Prepare in Production
The process will remain the same in the production environment as well. Simply visit profile settings, press on verification request, and follow the instructions you receive in your inbox.
10. Review and Update Settings to Capture Leads from LinkedIn
Due to some changes in the LinkedIn APIs, any Lead gen forms connected to the LinkedIn platform will need some revamping to function as usual.
Prepare in Sandbox
The preparation for this update is challenging as you need to assess your business processes properly. It would be helpful to determine which environment is best for changing and testing this update. Make sure to have a backup of your existing setups and configuration; in addition to the backup, set up a way to track missed leads during the migration period.
As per Salesforce, these are the steps to prepare for this update:
- Review your LinkedIn Lead Gen Settings.
- Disconnect your LinkedIn account.
- Turn on “Use LinkedIn Lead Sync APIs with Lead Forms”.
- Connect your LinkedIn account.
- Verify your LinkedIn Lead Gen Settings.
- Check for unsynced leads on LinkedIn.com.
- Review alert.
To Sum Up
The Salesforce Spring ’25 Release Notes will be updated on the Salesforce website right before the release. These notes are detailed documents on every update and how to navigate through the changes. Until then, you can prepare your Salesforce org with some basic settings to ensure a smoother migration to new updates. Follow the above guide to achieve maximum efficiency post-release. Stay tuned to our website for updates on the Spring release and further Salesforce updates coming along.
