Salesforce release updates
Updates made to the Salesforce platform can impact existing applications, such as Delphi. These updates can also impact additional customizations in your org. When Salesforce implements updates, they make it available as a 'Release Update.' Release updates are inactive for a period of time before automatically activated by Salesforce. During this period, the updates can be activated and deactivated by an administrator to review the impact and make any necessary changes before activation. More information on Salesforce Critical Updates and Salesforce Releases is available from Salesforce.
The Amadeus product team reviews Salesforce updates to ensure the updates are compatible with the current release of Delphi. Release updates can have auto-activation dates a year or more into the future. Amadeus reviews all release updates a minimum of 90 days before the auto-activation date. If your org requires an update to be compatible with the Salesforce update, we can notify you to have the latest version of Delphi installed.
Administrators need to be aware of any customizations in your org, no matter who implemented them. Administrators need to ensure ongoing compatibility of any customizations with the Salesforce platform and with new releases of Delphi. These customizations can include workflows, custom fields, validation rules, process flows, apex triggers, and other Salesforce configurations. These customizations cannot be managed by Amadeus. Administrators need to review the information provided by Salesforce for upcoming release updates and decide whether any changes to your customizations are required.
Delphi is Salesforce Lightning experience compatible.
The below table is modified when Salesforce introduces new release updates. Amadeus recommends reviewing this page often for additional information. To view current release updates in your org, click Setup and then enter 'Release Updates' in the Quick Find search box.
| Salesforce Critical Update | Verified / Safe to Activate |
|---|---|
| Adopt Updated Content Security Policy (CSP) Directives |
Yes |
| Enable LWC Stacked Modals |
Yes |
| Use REST API for Access to External Client App OAuth Consumer Credentials |
Yes |
| Enforce Sharing Rules when Apex Launches a Flow |
Yes |
| Create and Verify Your Default No-Reply Organization-Wide Email Address To Send Email | Yes |
| Enforce View Roles and Role Hierarchy Permission When Editing Public List View Visibility | Yes |
| Enable Secure Redirection for Screen Flows | Yes |
| Pass the Conversation Intelligence Rule Name As Input to a Flow | Yes |
| Prepare for the Japanese Katakana Style Change | Yes |
| Restrict User Access to Run Flows | Yes |
| Allow Only Trusted Cross-Org Redirections | Yes |
| Enable Faster Account Sharing Recalculation by Not Storing Case and Contact Implicit Child Shares | Yes |
| Sender Name and Email Address Required for Chatter Email Notifications to be Sent | Yes |
| Run Flows in Bot User Context | Yes |
| Salesforce Object ID Is Refined to Use Three Characters for Server IDs | Yes |
| Transition to the Lightning Editor for Email Composers in Email-to-Case | Yes |
| Enable EmailSimple Invocable Action to Respect Organization-Wide Profile Settings | Yes |
| Enable Visualforce JavaScript Remoting JsonAccess Annotation Enforcement | Yes |
| Salesforce Platform API Versions 21.0 through 30.0 Retirement | Yes |
| Enforce Rollbacks for Custom Invocable Action Exceptions in Connect REST API | Yes |
| Enforce RFC 7230 Validation for Apex RestResponse Headers | Yes |
| Not Yet Verified | |
| Enforce Permission Requirements Defined on Built-In Apex Classes Used as Inputs |
No |
| Migrate to a Multiple-Configuration SAML Framework |
No |
| Sort Apex Batch Action Results by Request Order |
No |
| Enforce Permission Requirements Defined on Built-In Apex Classes Used as Inputs |
No |
| Verify Your Return Email Address for Sender Verification |
No |
| Grant Access to the Label Object in Custom Profiles to Continue Using To Do List Labels |
No |