---
schema_version: "1"
id: 39d5c4c6655ca641560fa4fe6d60ad73750f844dcc8ff1f33de7844df16560b2
title: Release Updates
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_ru.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_ru.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: af852ebb9036c2f797dbede5d5cee836a0c6803f78bc5a1af9f28cd872a7ebcb
description: Salesforce periodically provides release updates that improve the performance, logic, security, and usability of our products. The Release Updates page provides a list of updates that can be necessary for your organization to enable. Some release updates affect existing customizations.
products:
  - Cross Cloud
release: "262"
---
# Release Updates

Salesforce periodically provides release updates that improve the performance, logic, security, and usability of our products. The Release Updates page provides a list of updates that can be necessary for your organization to enable. Some release updates affect existing customizations.

Every time a release update is created, it gets scheduled to be enforced in a future release. We announce each update and its schedule here as soon as that schedule is known, but occasionally, updates are postponed or canceled. If that happens, we let you know in the section that describes that specific release update.

Often, release updates provide a Test Run option so you can enable an update and examine any changes to your org, including changes to customizations, before that update’s Complete Steps By date. You can view attachments in the Salesforce mobile app, but you can’t edit them.

To view release updates, from Setup, in the Quick Find box, enter Release Updates, and select **Release Updates**.

## Enforced with This Release

These updates are scheduled to be enforced this release.

[Migrate to a Multiple-Configuration SAML Framework (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_saml_multi_config.htm&release=262.0.0&type=5 "If you see this release update, your Salesforce instance is using our original single-configuration SAML framework, which supports single sign-on (SSO) with only one identity provider. We’re giving you a final reminder that with Summer ’26, we no longer support the single-configuration SAML framework. To make sure that your SSO configurations don’t break, migrate to our newer multiple-configuration SAML framework, which supports SSO with multiple identity providers instead of just one. If you don’t migrate, your SAML SSO configurations will stop working when this release update is enforced in Summer ’26.")

If you see this release update, your Salesforce instance is using our original single-configuration SAML framework, which supports single sign-on (SSO) with only one identity provider. We’re giving you a final reminder that with Summer ’26, we no longer support the single-configuration SAML framework. To make sure that your SSO configurations don’t break, migrate to our newer multiple-configuration SAML framework, which supports SSO with multiple identity providers instead of just one. If you don’t migrate, your SAML SSO configurations will stop working when this release update is enforced in Summer ’26.

[Salesforce-Managed X (Formerly Twitter) Authentication Provider Retirement (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_twitter_provider_retirement.htm&release=262.0.0&type=5 "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.")

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.

[Sort Apex Batch Action Results by Request Order (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_release_update_sort_apex_batch_action_result_by_request_order.htm&release=262.0.0&type=5 "With this update enabled, Apex batch action results are shown in the order that the requests are received. Currently, error-prone requests are prioritized at the top of the result list, and successful requests are at the bottom.")

With this update enabled, Apex batch action results are shown in the order that the requests are received. Currently, error-prone requests are prioritized at the top of the result list, and successful requests are at the bottom.

[Use Visualforce PDF Rendering Service with Apex Blob.toPdf() (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_system_blob_topdf.htm&release=262.0.0&type=5 "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.")

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.

## Scheduled to Be Enforced in Winter ’27

These updates are scheduled to be enforced in Winter ’27. The list can include new, previously announced, and previously postponed release updates.

[Adopt Authorized Email Domains (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_adopt_authorized_email_domains.htm&release=262.0.0&type=5 "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. First available in Spring ’26, this update is enforced in Winter ’27.")

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. First available in Spring ’26, this update is enforced in Winter ’27.

[Enable Accessibility Enhancements for Page Headers and Modal Windows When Zoom Is Greater Than 200% (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_general_accessibility_page_headers_modals_ru_262.htm&release=262.0.0&type=5 "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 was scheduled to be enforced in Summer ’26, but we postponed the enforcement date to Winter ’27.")

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.

[Enable Accessibility Enhancements for Date Pickers, Popovers, Bottom Utility Bars, Record Headers (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_general_accessibility_datepicker_recordheaders_ru_262.htm&release=262.0.0&type=5 "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 was first available in Winter ’26 and was scheduled to be enforced in Summer ’26, but we postponed the enforcement date to Winter ’27.")

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.

[Enable Accessibility Enhancements for Cards, Docked Containers, Menu Lists, and Panels (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_general_accessibility_cards_docked_containers_ru_262.htm&release=262.0.0&type=5 "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. Make sure to enable that update first.")

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.

[Enable Profile Filtering (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_permissions_profile_filtering_ru.htm&release=262.0.0&type=5 "To improve the security of your Salesforce org, the Profile Filtering setting is enabled by default. Profile filtering prevents users from viewing profile names other than their own unless they’re 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.")

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’re 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.

[Modify Transaction Security Policy Permission](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_em_modify_tsp_perm.htm&release=262.0.0&type=5 "The new Modify Transaction Security Policy (TSP) permission provides an extra layer of control and security for your policies. This permission is required to create, delete, and update TSPs, and it supports Step-up Authentication for additional security. Users with only the Customize Application permission are now restricted to view-only access.")

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.

[Retirement of OAuth 2.0 Username-Password Flow for Connected Apps (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_unpw_flow_retirement.htm&release=262.0.0&type=5 "When this release update is enforced, 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.")

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.

## Scheduled to Be Enforced in Spring ’27

These updates are scheduled to be enforced in Spring ’27. The list can include new, previously announced, and previously postponed release updates.

[Enable Accessibility Enhancements for To Do Lists and Lightning Dual Listboxes When Zoom Is Greater Than 200% (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_general_accessibility_todo_listboxes_ru_262.htm&release=262.0.0&type=5 "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.")

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.

[Remove Non-Public Fields from Custom Object Data in Aura Action Responses (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_lc_rus_remove_nonpublic_fields_ru_262.htm&release=262.0.0&type=5 "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 aren’t part of the public Salesforce API. Review your Lightning components that process custom object data to avoid JavaScript errors or missing data. Use only API-supported fields in your components to ensure that your data displays correctly.")

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 aren’t part of the public Salesforce API.

[Salesforce to Salesforce Is Being Retired (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_salesforce_to_salesforce_retiring_ru.htm&release=262.0.0&type=5 "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.")

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.

[SOAP API login() Call in SOAP API Versions 31.0 Through 64.0 Is Being Retired (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_upcoming_retirement_262rn.htm&release=262.0.0&type=5 "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.")

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.

[Update Apex Code and Flows for Changed Sharing Recalculation Behavior (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_sharing_apex_recalc_ru.htm&release=262.0.0&type=5 "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, triggers, and flows that update group membership or roles if they rely on synchronous sharing recalculation. This update was first available in Spring ’26.")

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 was first available in Spring ’26.

[Update Instanced URLs in API Traffic (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_update_instanced_urls_in_api_traffic.htm&release=262.0.0&type=5 "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 was scheduled to be enforced in Spring ’26, but we postponed the enforcement date to Spring ’27.")

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 was scheduled to be enforced in Spring ’26, but we postponed the enforcement to Spring ’27.

## Scheduled to Be Enforced in Summer ’27

These updates are scheduled to be enforced in Summer ’27. The list can include new, previously announced, and previously postponed release updates.

[Block Apex Anonymous Code Execution from Managed Packages (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_block_exec_anon_ru.htm&release=262.0.0&type=5 "To strengthen subscriber org security, block managed package session IDs from authenticating anonymous Apex code. 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.")

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 Scheduled Enforcement Date

These updates have no planned enforcement date at this time. The list can include previously announced and previously postponed release updates.

[Enable ICU Locale Formats (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_globalization_enable_icu_locale.htm&release=262.0.0&type=5 "With this update, the International Components for Unicode (ICU) locale formats replace Oracle’s Java Development Kit (JDK) locale formats in Salesforce. Locales control the format for dates, times, currencies, addresses, names, numeric values, and the start day of the week. ICU sets the international standard for these formats. The ICU locale formats provide a consistent experience across the platform and improve integration with ICU-compliant applications across the globe. This update was first made available in Winter ’20. Orgs that haven’t already switched to ICU locale formats are encouraged to manually update.")

With this update, the International Components for Unicode (ICU) locale formats replace Oracle’s Java Development Kit (JDK) locale formats in Salesforce. Locales control the format for dates, times, currencies, addresses, names, numeric values, and the start day of the week. ICU sets the international standard for these formats. The ICU locale formats provide a consistent experience across the platform and improve integration with ICU-compliant applications across the globe. This update was first made available in Winter ’20. Orgs that haven’t already switched to ICU locale formats are encouraged to manually update.

[Enforcing No-Argument Constructor on Apex Classes Used for Invocable Action Parameters (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_release_update_enforce_perm_requirements_on_built_in_apex_classes.htm&release=262.0.0&type=5 "When this update is enabled, you get access to certain built-in Apex classes that are available to be used as invocable action parameters. Additionally, this update enforces the visibility of the no-argument constructor on any class. This update was scheduled to be enforced in Summer ’26. Starting in Spring ’26, Salesforce no longer enforces this update, but we recommend that you enable it. This release update was previously named Enforce Permission Requirements Defined on Built-In Apex Classes Used as Inputs.")

When this update is enabled, you get access to certain built-in Apex classes that are available to be used as invocable action parameters. Additionally, this update enforces the visibility of the no-argument constructor on any class. This update was scheduled to be enforced in Summer ’26. Starting in Spring ’26, Salesforce no longer enforces this update, but we recommend that you enable it. This release update was previously named Enforce Permission Requirements Defined on Built-In Apex Classes Used as Inputs.