With Spring '25 updates now fully rolled out, it’s time to ensure your Salesforce org is compliant and optimized for these changes. If you haven’t reviewed your settings yet, now is the time to double-check critical updates that took effect in January and February.

But the work doesn’t stop there! We’re already looking ahead to Summer '25, where major enforcement deadlines are approaching. Some of these updates—like retiring Classic Knowledge and older API versions—could break critical processes if your org isn’t prepared.

Key Takeaways for March 2025:

✔ Spring '25 enforcement is complete – Make sure all necessary updates are implemented.
✔ Summer '25 is coming fast – Start preparing now to avoid disruptions.
✔ Security and performance changes require action – Pay close attention to API retirements, SAML security upgrades, and Lightning Knowledge migration.

Not sure if your org is ready? We’ve outlined everything below, including what’s changed, what’s coming next, and how to prepare.

Spring '25 Release Updates

The Spring '25 update has rolled out to all Salesforce orgs, finishing at the end of February 2025. While some changes have been postponed, several still took effect.

Delayed or Optional Updates (Recommended but Not Enforced Yet)

These updates won’t be mandatory yet, but Salesforce still recommends preparing for them.

1. Rollback for Apex Action Exceptions (REST API) – No Longer Mandatory
   • Originally, Salesforce planned to enforce stricter handling of errors in custom code. Now, they recommend but don’t require making these changes.
   • If you use custom Apex code, it's still a good idea to adjust it for best performance and reliability.
2. Email Threading Behavior Update (Lightning Threading)
   • If you work with emails linked to Salesforce records, Salesforce wants you to switch to a new way of tracking conversations called “Lightning Threading.”
   • While enforcement has been delayed, it’s recommended to switch now for better email tracking.
3. New Email Editor for Email-to-Case (Service Cloud Users Only)
   • Salesforce introduced a new email editor with extra features like printing and full-screen mode.
   • The old editor is still available, but it will eventually be replaced. It’s best to switch now to get familiar with the new tools.
4. Secure Redirection for Flows
   • Salesforce was going to enforce a new security setting for Flows in February, but the update may not be finalized yet.
   • We’ll keep an eye on this in case Salesforce changes the enforcement date.
5. SAML Single Sign-On (SSO) Changes – Action Needed Before Spring ‘26
   • If your org uses SAML for logging into Salesforce, check your setup.
   • Some orgs will need to migrate to a new framework before Spring ‘26, or SSO may stop working.
6. Field Service Maintenance Work Rules – Mandatory by Winter '26
   • If you use Field Service, Salesforce is phasing out older scheduling methods for maintenance plans.
   • Instead of using "Frequency" fields, you’ll need to use Maintenance Work Rules starting Winter ‘26.

Spring '25 Updates That WILL Be Enforced (Action Required!)

These changes will take effect with the Spring '25 release, so make sure you're ready.

1. Einstein Activity Capture (EAC) Permissions Changing
   • If your team uses Sales Engagement Basic, it will no longer include access to Einstein Activity Capture (EAC).
   • You’ll need to assign EAC permissions separately or users may lose access.
2. Lightning Web Component (LWC) Stacked Modals
   • Salesforce is upgrading parts of its interface for better performance.
   • This will slightly change how pop-ups (modals) look and behave, especially if you use custom quick actions.
3. New Date, Time, and Currency Formatting (ICU Locale Formats)
   • Salesforce is switching to a new standard format for dates, times, and currencies.
   • Most users won’t notice a difference, but if you use custom code, it may need to be adjusted.
4. New Role Hierarchy Permissions for List Views
   • If you create list views (saved filters for records), you may no longer see the full company role hierarchy unless you have special permission.
   • Admins should check whether users will need additional permissions to manage list views.
5. Changes to Salesforce AI Prompts (For AI Flow Users)
   • If your org uses AI-powered flows, some older AI prompt templates will stop working.
   • You’ll need to update your flows to use the new prompt format.
6. LinkedIn Lead Capture Update – Immediate Action Needed
   • If you pull leads from LinkedIn into Salesforce, you must update your settings to continue using this feature.
   • This change took effect on December 16, 2024.
7. Sorting Order for Apex Batch Jobs Changing
   • If your system processes large numbers of records, Salesforce is changing how errors are reported.
   • Instead of failed batches appearing at the top of the list, they will now appear in the order they were processed.
8. MyDomain URL Enforcement for API Requests – Deadline June 14, 2025
   • If your system still uses old Salesforce API URLs, update them before June 14, 2025.
   • Salesforce will stop redirecting old URLs after that date.
9. New Email Verification Requirement
   • Salesforce will no longer send emails from unverified addresses.
   • Admins should check if any users need to verify their email addresses.

Summer '25 Release Updates

These updates will arrive in Summer 2025, so it’s good to prepare in advance.

Key Summer '25 Changes

1. Lightning Web Component (LWC) Updates for Aura Sites
   • If you use Experience Cloud, some pages will switch to LWC for faster loading and better accessibility.
   • Expect minor visual changes, like field shading and button alignment.
2. Process Builder Fix for Null Values (But You Should Move to Flow!)
   • Salesforce is fixing a bug in Process Builder, but since Process Builder support ends in December 2025, it’s smarter to migrate to Flow instead.
3. Salesforce Classic Knowledge is Going Away
   • If you still use Classic Knowledge, you’ll need to move to Lightning Knowledge before 2025.
4. Older Salesforce API Versions (21.0 - 30.0) Being Retired
   • If your org uses very old API versions (pre-2014), those will stop working.
   • Most orgs won’t be affected unless they rely on custom integrations.
5. Content Security Policy (CSP) Updates
   • Salesforce is tightening security for embedded content (like fonts or images from other sites).
   • Admins will need to update trusted site settings if anything stops loading properly.
6. SAML Security Upgrades – Test Your Setup!
   • Salesforce is improving security for SAML logins, which could affect single sign-on users.
   • Test your setup in a sandbox before Spring ‘25 to ensure smooth logins.

What Should You Do Next?

Not sure which updates affect your org? Check your Salesforce Release Updates in Setup.
Prolocity is here to help you navigate these changes! Let us know if you need assistance making updates before enforcement deadlines.