Case Split Release Notes 3.16

Case Split Release Notes 3.16 - 3.20.2

What's New

The Email(s) section in the Case Split page now displays additional information about the email messages, including Status, Subject, From, and Message Date. (3.18)

A new "Allow Field Truncation" setting has been added, allowing the truncation of fields that exceed their character limits and preventing errors during the split. (3.20)

Improvements

A new "Bypass Sharing and Security on Related Records" setting was added to bypass the org's current sharing model, avoiding errors when the user performing the split cannot access the new case. (3.16 and 3.17)
Our code was adjusted to better handle custom object settings when configuring the app to avoid errors similar to "You don't have apex class access to CaseSplitLWCController" and "Case Split Related Objects not configured, please contact admin to set up the Case Split Related Objects in Case Split Settings before splitting." (3.17)
To clean up any components no longer used in the package, the deprecated Case Split visualforce page was removed. (3.18)
Chatter Post is now on the list of standard Salesforce objects that can be displayed on the split page for selection. (3.19)
Improved error handling to display more descriptive error messages if an error happens during the split, instead of the generic "Script Thrown Exception" error displayed today. (3.20)

Bugs Fixed

An issue where an "Attempt to de-reference a null object" error message showed up when generating the successfully split case comment was fixed. (3.16)

We fixed an issue in the setup wizard where settings with toggle controls could be toggled on/off by clicking outside the switch. (3.18)
The issue of email messages not showing up on the split page due to custom case lookup fields to the Email Message object has been fixed. (3.18)
The "DUPLICATE_VALUE, The member you have selected is already on the team. Please select another." error should no longer show up if the user performing the split is already part of the Case Team. (3.19)
Fixed " Insert failed. First exception on row 0; first error: STRING_TOO_LONG, HTML Body: data value too large" errors when the "Allow Field Truncation" setting is enabled. (3.20.1)
The error "Cannot read properties of undefined (reading 'recordPickerBase')" has been fixed and will no longer show up when splitting to existing cases. (3.20.2)

Title

Case Split Release Notes 3.16 - 3.20.2