Regression testing results - 2024
Summer '24 test results
In response to the Salesforce Summer '24 release, Mavens regression tested critical updates and updates that were identified as potentially having a significant impact on the Scientific Publications Cloud product. Testing occurred in out-of-the-box Scientific Publications Cloud Fall '23 and Spring '24 environments. Scientific Publications Cloud is considered out-of-the-box when no custom code, customizations, or configurations, such as custom integrations, custom formulas, or custom workflows, have been added to the product.
Scientific Publications Cloud Spring '24 environment
The table below lists the specific updates that were tested in a Scientific Publications Cloud Spring '24 environment and the test results. Updates that passed regression testing have a checkmark in the Passed column. A checkmark means that the update did not inhibit core Scientific Publications Cloud functionality.
Spring '24 environment test results
| Update tested | Passed | Notes |
|---|---|---|
| Allow Only Trusted Cross-Org Redirections | ✓ | |
| Enable EmailSimple Invocable Action to Respect Organization-Wide Profile Settings | ✓ | |
| Run Flows in Bot User Context | ✓ | |
| Enforce Sharing Rules when Apex Launches a Flow | ✓ | |
| Enforce View Roles and Role Hierarchy Permission When Editing Public List View Visibility | ✓ | |
| Prevent Guest User from Editing or Deleting Approval Requests | ✓ | |
| Restrict User Access to Run Flows | ✓ | |
| Disable Ref ID and Transition to New Email Threading Behavior | ✓ | |
| Enable Secure Redirection for Flows | ✓ | |
| Enable New Order Save Behavior | ✓ | |
| Enforce Rollbacks for Apex Action Exceptions in REST API | ✓ | |
| Transition to the Lightning Editor for Email Composers in Email-to-Case | ✓ | |
| Enable ICU Locale Formats | ✓ | |
| Evaluate Criteria Based on Original Record Values in Process Builder | ✓ | |
| Salesforce Platform API Versions 21.0 through 30.0 Retirement | ✓ | Scientific Publications Cloud uses API versions 52.0 and above. |
| Adopt Updated Content Security Policy (CSP) Directives | When this is enforced in an org with the Office 365 integration, you must configure Office 365 as a trusted site to ensure that Office 365 iframes load as expected. For more information, reference KI-121. | |
| Create and Verify Your Default No-Reply Organization-Wide Email Address To Send Email | ✓ | When this is enforced, you will need to use an organization-wide default email address to ensure that system event notifications are sent. |
| Disable Access to Session IDs in Flows | ✓ | |
| Use REST API for Access to External Client App OAuth Consumer Credentials | ✓ | |
| Use an Apex-Defined Variable for All Intelligence Signal Types | ✓ | |
| Migrate to a Multiple-Configuration SAML Framework | ✓ | |
| Enable Partial Save for Invocable Actions | ✓ | |
| Migrate from Maintenance Plan Frequency Fields to Maintenance Work Rules | ✓ | |
| Make Flows Respect Access Modifiers for Legacy Apex Actions | ✓ | |
| Enable LWC Stacked Modals | ✓ | |
| Sort Apex Batch Action Results by Request Order | ✓ | |
| Pass the Conversation Intelligence Rule Name as Input to a Flow | ✓ | |
| Run Flows in User Context via REST API | ✓ | |
| Turn On Lightning Article Editor and Article Personalization for Knowledge | ✓ | |
| Enforce Permission Requirements Defined on File-Based Apex Classes Used as Inputs | ✓ | |
| Google Chrome Storage Partitioning | ✓ | These are not release updates but optional features that will be enforced by Salesforce in the future. Turning on these features does not inhibit any core functionality in the current Scientific Publications Cloud product. |
| Require First Party Cookies | ✓ | |
| Switch to a Single Domain Certificate for Your Salesforce Content Delivery Network | ✓ | |
| Lightning Web Security | ✓ |
Scientific Publications Cloud Fall '23 environment
The table below lists the specific updates that were tested in a Scientific Publications Cloud Fall '23 environment and the test results. Updates that passed regression testing have a checkmark in the Passed column. A checkmark means that the update did not inhibit core Scientific Publications Cloud functionality.
Fall '23 environment test results
| Update tested | Passed | Notes |
|---|---|---|
| Allow Only Trusted Cross-Org Redirections | ✓ | |
| Enable EmailSimple Invocable Action to Respect Organization-Wide Profile Settings | ✓ | |
| Run Flows in Bot User Context | ✓ | |
| Enforce Sharing Rules when Apex Launches a Flow | ✓ | |
| Enforce View Roles and Role Hierarchy Permission When Editing Public List View Visibility | ✓ | |
| Prevent Guest User from Editing or Deleting Approval Requests | ✓ | |
| Restrict User Access to Run Flows | ✓ | |
| Disable Ref ID and Transition to New Email Threading Behavior | ✓ | |
| Enable Secure Redirection for Flows | ✓ | |
| Enable New Order Save Behavior | ✓ | |
| Enforce Rollbacks for Apex Action Exceptions in REST API | ✓ | |
| Transition to the Lightning Editor for Email Composers in Email-to-Case | ✓ | |
| Enable ICU Locale Formats | ✓ | |
| Evaluate Criteria Based on Original Record Values in Process Builder | ✓ | |
| Salesforce Platform API Versions 21.0 through 30.0 Retirement | ✓ | Scientific Publications Cloud uses API versions 52.0 and above. |
| Adopt Updated Content Security Policy (CSP) Directives | When this is enforced in an org with the Office 365 integration, you must configure Office 365 as a trusted site to ensure that Office 365 iframes load as expected. For more information, reference KI-121. | |
| Create and Verify Your Default No-Reply Organization-Wide Email Address To Send Email | ✓ | When this is enforced, you will need to use an organization-wide default email address to ensure that system event notifications are sent. |
| Disable Access to Session IDs in Flows | ✓ | |
| Use REST API for Access to External Client App OAuth Consumer Credentials | ✓ | |
| Use an Apex-Defined Variable for All Intelligence Signal Types | ✓ | |
| Migrate to a Multiple-Configuration SAML Framework | ✓ | |
| Enable Partial Save for Invocable Actions | ✓ | |
| Migrate from Maintenance Plan Frequency Fields to Maintenance Work Rules | ✓ | |
| Make Flows Respect Access Modifiers for Legacy Apex Actions | ✓ | |
| Enable LWC Stacked Modals | ✓ | |
| Sort Apex Batch Action Results by Request Order | ✓ | |
| Pass the Conversation Intelligence Rule Name as Input to a Flow | ✓ | |
| Run Flows in User Context via REST API | ✓ | |
| Turn On Lightning Article Editor and Article Personalization for Knowledge | ✓ | |
| Enforce Permission Requirements Defined on File-Based Apex Classes Used as Inputs | ✓ | |
| Google Chrome Storage Partitioning | ✓ | These are not release updates but optional features that will be enforced by Salesforce in the future. Turning on these features does not inhibit any core functionality in the current Scientific Publications Cloud product. |
| Require First Party Cookies | ✓ | |
| Switch to a Single Domain Certificate for Your Salesforce Content Delivery Network | ✓ | |
| Lightning Web Security | ✓ |
Spring '24 test results
In response to the Salesforce Spring '24 release, Mavens regression tested critical updates and updates that we identified as potentially having a significant impact on the Scientific Publications Cloud product. Testing occurred in an out-of-the-box Scientific Publications Cloud environment. Scientific Publications Cloud is considered out-of-the-box when no custom code, customizations, or configurations, such as custom integrations, custom formulas, or custom workflows, have been added to the product.
Scientific Publications Cloud Fall '23 environment
The table below lists the specific updates that were tested in a Scientific Publications Cloud Fall '23 environment and the test results. Updates that passed regression testing have a checkmark in the Passed column. A checkmark means that the update did not inhibit core Scientific Publications Cloud functionality.
Fall '23 environment test results
| Update tested | Passed | Notes |
|---|---|---|
| Enable JsonAccess Annotation Validation for the Visualforce JavaScript Remoting API | ✓ | |
| Enforce RFC 7230 Validation for Apex RestResponse Headers | ✓ | All headers used for the Scientific Publications Cloud Collaborator Portal are valid. |
| Enable Faster Account Sharing Recalculation by Not Storing Case and Contact Implicit Child Shares | ✓ | |
| Enable Faster Account Sharing Recalculation by Not Storing Opportunity Implicit Child Shares | ✓ | |
| Allow Only Trusted Cross-Org Redirections | ✓ | |
| Enable EmailSimple Invocable Action to Respect Organization-Wide Profile Settings | ✓ | |
| Enable New Order Save Behavior | ✓ | |
| Enable ICU Locale Formats | ✓ | |
| Evaluate Criteria Based on Original Record Values in Process Builder | ✓ | |
| Salesforce Platform API Versions 21.0 through 30.0 Retirement | ✓ | |
| Run Flows in Bot User Context | ✓ | |
| Transition to the Lightning Editor for Email Composers in Email-to-Case | ✓ | |
| Enforce Sharing Rules when Apex Launches a Flow | ✓ | |
| Enforce View Roles and Role Hierarchy Permission When Editing Public List View Visibility | ✓ | |
| Prevent Guest User from Editing or Deleting Approval Requests | ✓ | |
| Restrict User Access to Run Flows | ✓ | |
| Disable Ref ID and Transition to New Email Threading Behavior | ✓ | |
| Enable Secure Redirection for Screen Flows | ✓ | |
| Enforce Rollbacks for Apex Action Exceptions in REST API | ✓ | |
| Keep Working with Tab-Focused Dialogs | Postponed. | |
| Prevent consecutive API navigation calls | Postponed. | |
| Lightning Web Security | ✓ |
Winter '24 test results
In response to the Salesforce Winter '24 release, Mavens regression tested critical updates and updates that we identified as potentially having a significant impact on the Scientific Publications Cloud product. Testing occurred in an out-of-the-box Scientific Publications Cloud environment. Scientific Publications Cloud is considered out-of-the-box when no custom code, customizations, or configurations, such as custom integrations, custom formulas, or custom workflows, have been added to the product.
Scientific Publications Cloud Spring '23 environment
The table below lists the specific updates that were tested in a Scientific Publications Cloud Spring '23 environment and the test results. Updates that passed regression testing have a checkmark in the Passed column. A checkmark means that the update did not inhibit core Scientific Publications Cloud functionality.
Spring '23 environment test results
| Update tested | Passed | Notes |
|---|---|---|
| Deploy Enhanced Domains | ✓ | If enabling Enhanced Domains for the first time in a Salesforce org that already has an established implementation of the Scientific Publications Cloud product and the Collaborator Portal, you must follow the following steps: 1. Two days prior to enabling Enhanced Domains in any Salesforce org, notify Mavens. 2. When you enable Enhanced Domains and a new Collaborator Portal URL is generated, share the URL with your Mavens representative. 1. The Mavens product team will use that new URL to update the backend to ensure there is no outage as a result of enabling Enhanced Domains. |
| Disable Access to Session IDs in Flows | ✓ | |
| Enable Faster Account Sharing Recalculation by Not Storing Case and Contact Implicit Child Shares | ✓ | |
| Make Paused Flow Interviews Resume in the Same Context | ✓ | The Scientific Publications Cloud product uses flows, but none of the flows use pause elements. |
| Prepare for the Japanese Katakana Style Change | ✓ | |
| Require Sender Name and Email Address to Send Chatter Email Notifications | ✓ | |
| Salesforce Object ID is Refined to Use Three Characters for Server IDs | ✓ | |
| Security Enhancements for CSRF Tokens for Lightning Apps | ✓ |