Salesforce® Spring ’26 Release: Key Updates & Action Items Copy
- News
- Healthcare & Life Sciences
- Salesforce
- Salesforce Partners
- Salesforce Releases
Prepare for the Salesforce® Spring ’26 Release: Key Updates and What to Do Next
The Salesforce® Spring ’26 release is here and is begin rolling out. This release delivers enhancements across order management, security and access. Each change is designed to help you work smarter, stay secure, and make the most of Salesforce®’s evolving platform.
Here’s everything you need to know about the upcoming changes, along with action items to ensure your organisation is ready.
Key Changes and What They Mean for Your Organisation
1. Calculate Tax-Only and Product-Only Price Adjustments
Salesforce® is improving how tax and product pricing is calculated when making pricing adjustments. This is only applicable to Salesforce® Order Management, which falls under Salesforce® Commerce Cloud.
Why it matters: It gives organisations more flexibility, discounts or adjustments can be applied to just the product price, just the tax or both, rather than as a single combined amount.
What to do: Nothing immediately for most users, but teams using complex pricing or tax rules may want to review their pricing setups or test how adjustments behave in quotes/orders going forward.
2. Escape the Label Attribute of <apex:inputField> Elements to Prevent XSS in Visualforce
A security enhancement that adds an extra layer of protection to help keep your Visualforce pages safe from malicious code that could try to run through your website, such as cross-site scripting (XSS) attacks.
Why it matters: It improves the safety and trustworthiness of Salesforce® environments, particularly for orgs still using Visualforce UI.
What to do: If Visualforce pages are used, fields and labels should be tested to ensure they still display correctly. Most changes will be invisible to users but older custom screens may require minor adjustments.
3. Update Instanced URLs in API Traffic
Salesforce® is phasing out references to old instance-based URLs (e.g. yourcompanyname.salesforce.com). Instead, orgs should use their My Domain URL or the updated standard domain format.
Why it matters: Older hard-coded URLs may stop working once Salesforce® removes support. This affects integrations, API connections, bookmarks and any systems that link directly to Salesforce®.
What to do: Review systems or integrations that connect to Salesforce®, and update them to use your My Domain URL instance domains. This prevents disruption in the future.
4. Migrate to a Multiple-Configuration SAML Framework
Salesforce® is replacing the old single-provider SAML login method with a more modern version that supports multiple identity providers.
Why it matters: Organisations using Single Sign-On (SSO) must move to the new framework; otherwise, login via SAML may stop working when the enforcement occurs.
What to do: If you use SSO, the configuration must be migrated and tested – ideally first in a sandbox. No action is needed for customers who do not use SAML-based login.
Key Dates
The releases will be released to Production (depending on instance):
- 10 January 2026: First release weekend
- 14 February 2026: Second release weekend
- 21 February 2026: Third release weekend
To do: Review the release notes, test updates in your sandbox environment, train relevant teams, and participate in Salesforce®’s preview webinars for live demonstrations.
By preparing early and staying informed, you can leverage the Salesforce® Spring ’26 release to optimise processes, enhance productivity, and stay ahead of the curve.
If you’d like Mint® to support your organisation in adopting these changes, get in touch with our team today!
Stay prepared. Stay productive. Stay ahead.