Salesforce release updates
Salesforce release updates made to the Salesforce platform may have an impact on existing applications, such as Amadeus Sales & Event Management. These updates may also have an impact on additional customizations in your org. When Salesforce implements such a change, they make it available as a “Release Update”. Release updates are initially inactive for a period of time before they are automatically activated by Salesforce. During this initial period, they can be activated and deactivated by an administrator of an org. This gives application developers and administrators an opportunity to review the potential impact and make any necessary changes before activating the update. More information on Salesforce Critical Updates and Salesforce Releases is available from Salesforce.
The Amadeus product team reviews the release updates and certifies that they are compatible with the current releases of our applications. Release updates can have activation dates a year or more into the future. Amadeus reviews all release updates a minimum of 90 days ahead of their auto-activation date. If your Amadeus application requires an update in order to be compatible with the Salesforce release update, we will notify you in advance of the auto-activation date in order to arrange to have the latest version of the Amadeus application installed in your org.
If you are an administrator of a Salesforce org, we strongly encourage you to be aware of any customizations in your org, whether implemented by you or someone else—including Amadeus—on your behalf. It is your responsibility as an administrator to ensure ongoing compatibility of any customizations with the Salesforce platform and with new releases of Amadeus applications. These customizations may include workflows, custom fields, validation rules, process flows, apex triggers, and other Salesforce configurations employed to meet your unique business requirements. It is important that you understand and maintain these customizations, as they are outside of the standard Amadeus application and cannot be managed by Amadeus. Administrators must review the information provided by Salesforce for upcoming release updates to determine if any changes to your customizations are required.
The below table is updated as Salesforce introduces new release updates. Please check back regularly for additional information. To view current release updates in your org, click Setup and then enter Release Updates in the quick find box.
| Salesforce Critical Update | Salesforce Release (introduced in) | Certified Version | Verified / Safe to Activate | Additional Notes |
|---|---|---|---|---|
| Enable Secure Redirection for Screen Flows | Spring ‘25 | R52 | Yes | Enforcement Scheduled Spring '25 |
| Pass the Conversation Intelligence Rule Name As Input to a Flow | Summer '24 | R51 | Yes | Enforcement Scheduled Summer ‘24 |
| MFA Auto-Enablement Continues: Find Out When and How Your Org Is Affected | Spring '24 | R50 | Yes | Enforcement Scheduled Summer '24 |
| Prepare for the Japanese Katakana Style Change | Winter '24 | R50 | Yes | Enforcement Scheduled Winter '24 |
| Restrict User Access to Run Flows | Winter '24 | R50 | Yes | Enforcement Scheduled Winter '25 |
| Allow Only Trusted Cross-Org Redirections | Winter '24 | R50 | Yes | Enforcement Scheduled Summer '24 |
| Enable Faster Account Sharing Recalculation by Not Storing Case and Contact Implicit Child Shares | Winter '24 | R49 | Yes | Enforcement Scheduled Winter '24 |
| Sender Name and Email Address Required for Chatter Email Notifications to be Sent | Summer '23 | R49 | Yes | Enforcement Scheduled Winter '24 |
| Run Flows in Bot User Context | Summer '24 | R49 | Yes | Enforcement Scheduled Winter '24 |
| Transition to the Lightning Editor for Email Composers in Email-to-Case | Winter '24 | R49 | Yes | Enforcement Scheduled Winter '24 |
| Salesforce Object ID Is Refined to Use Three Characters for Server IDs | Summer '23 | R49 | Yes | Enforcement Scheduled: Winter '24 |
| Transition to the Lightning Editor for Email Composers in Email-to-Case | Summer '23 | R49 | Yes | Enforcement Scheduled: Winter '24 |
| Enable EmailSimple Invocable Action to Respect Organization-Wide Profile Settings | Spring '24 | R49 | Yes | Enforcement Scheduled Spring '24 |
| Enable ICU Locale Formats | Spring '23 | R49 | Yes | Enforcement Scheduled Spring '24 |
| Enable Visualforce JavaScript Remoting JsonAccess Annotation Enforcement | Summer '23 | R48 | Yes | Enforcement Scheduled Winter '24 |
| Salesforce Platform API Versions 21.0 through 30.0 Retirement | Summer '23 | R48 | Yes | Enforcement Scheduled Summer '23 |
| Enforce Rollbacks for Custom Invocable Action Exceptions in Connect REST API | Winter '24 | R48 | Yes | Enforcement Scheduled Winter '24 |
| Enforce RFC 7230 Validation for Apex RestResponse Headers | Spring '24 | R48 | Yes | Enforcement Scheduled Spring '24 |
| Hyperforce Compatibility | R47 | Yes | For more information, see Release Notes dated June 28th. | |
| Not Yet Verified | ||||
| Enable Secure Static Resources for Lightning Components | Summer '24 | No | This release update has been postponed indefinitely while we change the implementation to reduce customer impact. The release update won’t be enforced in its present form. Do not enable it. | |
| Enforce View Roles and Role Hierarchy Permission When Editing Public List View Visibility | Winter ‘25 | No | ||
| Keep Working with Tab-Focused Dialogs | No | This release update has been postponed indefinitely while we change the implementation to reduce customer impact. The release update won’t be enforced in its present form. Do not enable it. | ||
| Escape Expression Language Evaluations in script and style Contexts in Visualforce Pages and Components | No | This release update has been canceled. Do not enable it. | ||