Summer '24 test results
In response to the Salesforce Summer '24 release, Komodo Health regression tested critical updates and updates that we identified as potentially having a significant impact on the Medical Information Cloud product. Testing occurred in V13 and V14 out-of-the-box Medical Information Cloud environments. Medical Information 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.
V14 test results
Table 74, “V14 Summer '24 regression testing” lists the specific updates that were tested in a V14 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 Medical Information Cloud functionality.
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 | ✓1 | |
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 | ✓ | |
Adopt Updated Content Security Policy (CSP) Directives | Fail | When this is enforced in an org with the Microsoft 365™ integration, you must configure Microsoft 365™ as a trusted site to ensure that Microsoft 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 Medical Information Cloud product. |
Require First Party Cookies | ✓ | |
Switch to a Single Domain Certificate for Your Salesforce Content Delivery Network | ✓ | |
Lightning Web Security | ✓ |
V13 test results
Table 75, “V13 Summer '24 regression testing” lists the specific updates that were tested in a V13 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 Medical Information Cloud functionality.
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 | ✓1 | |
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 | ✓ | |
Adopt Updated Content Security Policy (CSP) Directives | Fail | When this is enforced in an org with the Microsoft 365™ integration, you must configure Microsoft 365™ as a trusted site to ensure that Microsoft 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 Medical Information Cloud product. |
Require First Party Cookies | ✓ | |
Switch to a Single Domain Certificate for Your Salesforce Content Delivery Network | ✓ | |
Lightning Web Security | Fail | Fail is due to Known Issue KI-88. Not a release update, but an optional Salesforce feature. |
Footnote #1
For customers currently using the custom Apex email handler MED_InboundEmailHandler, ensure that it is enabled. No other action is necessary. The handler does not depend on threading, although V14.1 does use Lighting Threading as an optional fallback to improve matching on cases.
For customers using Email-to-Case, Komodo Health recommends you begin planning. Salesforce documentation suggests that it lacks a smooth transition plan if using a “faked” Thread ID (i.e., the only way to set the ID on child objects) when sending emails from non-Case objects. Currently, you are unable to get the new Lightning Thread token without enabling Lightning Threading. That said, as soon as you do enable Lightning Threading, the old thread ID tokens stop working. This means that the moment Lightning Threading is enabled, any previously sent emails will no longer route replies correctly and will create new cases instead.
There are two options for managing this:
Accept that there will be duplicate cases for a period of time after the transition and have agents manually make corrections as HCPs reply to old emails and create new cases.
Migrate to the custom email handler before Lightning Threading is enforced. Unlike the Thread ID to Email Token transition, Email-to-Case to MED_InboundEmailHandler should be much smoother as the custom Apex handler will route old emails back to the original record even though they were sent using Email-to-Case. It also seamlessly handles the Lightning Threading transition.