|
Update Name
|
Update Summary
|
ServiceMax Core
|
ServiceMax Go
|
ServiceMax Sync Gateway
|
ServiceMax Engage
|
ServiceMax Service Board
|
ServiceMax Data Guide
|
||
|---|---|---|---|---|---|---|---|---|---|
|
Auto Activation Date - Winter '26
|
|||||||||
|
With this update enabled, Salesforce restricts a user’s ability to run a flow. A user must be granted the correct profile or permission set to run the flow. When enabled, this release update deprecates the FlowSites org permission, which gave all users in the org access to run any flow. With this update, flows run more securely because only users who are granted correct profiles or permission sets can run flows. Salesforce postponed the enforcement to allow additional time for admins to test and prepare for the change. There is no impact to admins who already enabled the update. We appreciate your adoption of this change.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||
|
To comply with the latest email security standards, only users with a verified email address can send email from Salesforce. This change affects user accounts created on or before November 1, 2016. User accounts created after that date already can’t send emails unless their email address is verified.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||
|
To prevent unintended access by external site users if you enable digital experiences, Salesforce now secures access to records. The default sharing group that’s available for roles and subordinates before you enable digital experiences is now displayed as Roles and Internal Subordinates instead of as Roles and Subordinates. To prepare for this change, update code and customizations that reference the old group name. Although Salesforce dynamically converts outdated references during a transition period, you must update all code and customizations to prevent errors. This update was first available in Summer ’25 and is enforced in Winter ’26.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||
|
To prevent disruption when Salesforce ends support for API traffic that uses an incorrect instanced URL, make sure that API traffic to your org uses the org’s My Domain login URL. First available in Summer ’25, this release update is enforced in sandboxes Winter ’26 and is enforced in all other orgs in Spring ’26.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||
|
Starting in Winter '26, access to Service Assistant is provided only through the Service Planner User permission set license. At that time, permissions for Service Assistant will be removed from the Salesforce license, and feature access through that license isn't available. Admins must assign feature access to users using the Service Assistnat permssion set license.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||
|
Auto Activation Date - Spring '26
|
|||||||||
|
To prevent disruption when Salesforce ends support for API traffic that uses an incorrect instanced URL, make sure that API traffic to your org uses the org’s My Domain login URL. First available in Summer ’25, this release update is enforced in sandboxes Winter ’26 and is enforced in all other orgs in Spring ’26.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||
|
Prevent disruption for your customers and end users when the temporary redirection of legacy (non-enhanced) Salesforce host names ends. With this release update, legacy host name redirections end in production and demo orgs. Those redirections already ended in all other orgs in Winter ’25. First available in Spring ’25, this update is automatically enabled in Winter ’26 and is enforced in Spring ’26.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||
|
Incorporate tax-only and product-only adjustments into tax rate calculations during order processing. This update is enforced in Spring ’26
|
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 page headers and modal windows when viewed at high magnification. This is the beginning of our effort to comply with WCAG 2.2 Resize and Reflow guidelines. Expect accessibility enhancements to other UI elements in future release updates. This update was first available in Summer ’25 and is enforced in Spring ’26
|
• Functional Impact: No impact observed on ServiceMax Core product functionalities. All features continue to work as expected.
• UI Impact: Minor UI distortions were observed on a few screens only when the browser zoom level exceeds 200%. These issues are limited to visual presentation and do not affect usability or accessibility at standard zoom levels.
Mitigation Plan:
• The identified UI distortions will be addressed in upcoming ServiceMax product releases.
|
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 on Go client side
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||
|
Auto Activation Date - Summer '26
|
|||||||||
|
The Salesforce-managed app for the X (formerly Twitter) authentication provider is being retired. This update breaks any single sign-on (SSO) configurations that use the Salesforce-managed X app. To avoid disruptions, create a custom X app and update your SSO configurations.
|
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 date pickers, popovers, bottom utility bars, and record headers 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. Make sure to enable that update first. This update is available starting in Winter '26 and enforced in Summer ’26.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||
|
With this update enabled, the Apex Blob.toPdf() method for PDF rendering uses the same rendering service as Visualforce. The Visualforce PDF rendering service offers improvements such as additional fonts and multibyte character support. This change makes PDF rendering more consistent on the Salesforce Platform.
|
The new Visualforce PDF rendering service offers an expanded range of fonts, and the default font is changed from Serif to Sans-serif. If your PDF string doesn’t include explicit font styling, this change might result in different line lengths, and different line and page breaks for PDFs rendered compared to the old service.
|
The default font has been changed from Serif to Sans-serif in Salesforce.
No impact if the default font has been overwritten by customers.
|
The default font has been changed from Serif to sans-serif in Salesforce.
No impact if the default font has been overwritten by customers.
|
No Impact
|
No Impact
|
No Impact
|
|||
|
Update Einstein Activity Capture and migrate existing email data to the new data structure. Captured email data is now stored as Salesforce activity, making it available to standard reports and tools. After you start the migration, the process runs and completes automatically. This update is available starting in Winter '26 and enforced in Summer ’26.
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
No Impact
|
|||