|
Update Name
|
Update Summary
|
ServiceMax Core
|
ServiceMax Go
|
ServiceMax Sync Gateway
|
ServiceMax Engage
|
ServiceMax Service Board
|
ServiceMax Data Guide
|
|---|---|---|---|---|---|---|---|
|
Auto Activation Date - Winter '27
|
|||||||
|
To improve the security of your Salesforce org, Salesforce is enabling the Profile Filtering setting by default. Profile filtering prevents users from viewing profile names other than their own unless they are assigned the View All Profiles permission. If a user’s role requires them to see all profile names, assign them the View All Profiles permission before this release update is enforced. This update is available starting in Summer ’26.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|
|
The new Modify Transaction Security Policy permission gives you an extra layer of security control for your TSPs. This user permission is needed to perform create, delete and update TSPs. Users with the Customize Application permission are now restricted to view-only access.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|
|
In Winter ’27, we'll stop supporting the OAuth 2.0 username-password flow for connected apps. This update will break all connected app integrations that use this flow. For better security, update your integrations to use the OAuth 2.0 web-server flow or the OAuth 2.0 client credentials flow instead.
|
No Impact
|
No Impact
|
Impact
|
No Impact
|
Impact
|
No Impact
|
|
|
If you previously worked with Salesforce Customer Support to disable email change verifications, set up authorized email domains instead. Salesforce is retiring the existing exemption process for disabling this feature, and authorized email domains provide the same benefit.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|
|
To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of cards, docked containers, menu lists, and panels when viewed at high magnification. This release update is dependent on the Enable Accessibility Enhancements for Page Headers and Modal Windows When Zoom Is Greater Than 200% release update.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|
|
Auto Activation Date - Spring '27
|
|||||||
|
To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of To Do lists and Lightning dual listboxes when viewed at high magnification. This is part of our effort to comply with WCAG 2.2 Resize and Reflow guidelines.
|
Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|
|
To improve security, Salesforce is removing non-public system fields from custom object data returned in Aura action responses. This update filters out internal system fields that are not part of the public Salesforce API.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|
|
Salesforce to Salesforce is being retired in Spring ’27. Salesforce has more powerful and integrated solutions that align with modern business needs. To prevent disruption when Salesforce ends support for the Salesforce to Salesforce product, make sure that you migrate your integrations to one of these recommended solutions: Partner Cloud, Data Cloud One, MuleSoft Anypoint, or MuleSoft for Flow.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|
|
To optimize performance after large-scale updates to groups or roles, Salesforce now performs some sharing recalculations asynchronously. If Apex code and flows require that share records be updated immediately, the code and flows can break when this release update is enforced. Update Apex classes, tests, and flows that update group membership or roles if they rely on synchronous sharing recalculation. This update is available starting in Spring ’26.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|
|
Auto Activation Date - Summer '27
|
|||||||
|
Block managed package session IDs from authenticating anonymous Apex code blocks. If you enable this update, installed managed packages can no longer use `UserInfo.getSessionId()` to obtain a session ID, and then use the session ID to execute anonymous Apex. This update strengthens subscriber org security.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|
|
In Summer ‘27, the SOAP API login() call in SOAP API versions 31.0 through 64.0 will no longer be supported and no longer be available.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|