This release centers around the complete redesign of the Merge page, rebuilt as a Lightning Web Component with a modern interface and updated branding. The new page includes automatic async merge detection, notifying agents the moment a background merge completes, and the retired "Bypass Limit with Clean Merge" setting has been absorbed directly into Clean Merge — no separate configuration is required. Clean Merge notification messaging has also been rewritten to more clearly explain what will happen before agents proceed. A handful of smaller UI and reliability issues introduced by the redesign round out this cycle.

 

 

Action Items:

1. "Bypass Limit with Clean Merge" Setting Removed — The "Bypass Limit with Clean Merge" setting has been removed from the setup wizard. Admins who previously relied on this setting should verify that "Clean Merge" is enabled. When it is, the bypass now applies automatically whenever the number of selected cases exceeds the configured merge limit. No separate setting is needed. (v5.85)

UI/UX

The Merge page has been fully redesigned as a Lightning Web Component, replacing the legacy Visualforce page with a modern interface and updated branding. The retired "Bypass Limit with Clean Merge" setting has been absorbed into the "Clean Merge" setting. When Clean Merge is enabled, the bypass applies automatically based on the configured case limit, removing a configuration step that was easy to miss.

Case Merge Premium now automatically detects when a merge needs to run asynchronously. When that happens, agents see an in-page notification and can navigate away while the merge completes in the background. A toast notification appears when the merge is done, keeping agents informed without requiring them to stay on the merge page.

The Clean Merge notification messages have been updated to more clearly communicate what a Clean Merge does, when it will be triggered, and what choices are available. Agents now see messaging that explicitly explains the process — that child case records are closed as duplicates without transferring data to the primary case — along with clearly labeled options to proceed, refine their selection, or cancel.

Merge Page Errors in the Mobile Salesforce App — Several issues prevented the Merge page from loading and functioning correctly in the mobile Salesforce app, including a JavaScript error triggered by a utility bar call that does not apply in the mobile context. The page now loads and operates correctly on mobile. (v5.92)

External Client App List Truncated When More Than 10 Apps Exist — The "Configure External Client App or Connected App" setting in the setup wizard failed to display the full list of available External Client Apps when more than 10 were present in the org. Metadata retrieval calls are now batched correctly, and the complete list is returned. (v5.92)

Edit Icons for Fields on the Merge Page Not Working — The edit pencil icons for most fields on the new merge page were non-functional, preventing agents from modifying field values before completing a merge. Fields can now be edited as expected. (v5.91)

"Merge Cases" Button Appeared Transparent — The Merge Cases button in the Duplicate Detector component displayed with no visible background color, appearing transparent until hovered. The button now renders with a consistent, visible background. An incorrect tooltip that displayed the product name on hover has also been removed. (v5.91)

Intermittent Errors From Schema Calls Executing at Class Load Time — Some customers encountered intermittent errors caused by a schema call that ran at class load time, even when its value was not needed for the operation being performed. Schema calls are now deferred and execute only when required, eliminating these intermittent errors. (v5.90)

Oldest Case Not Selected as Default Primary on the New Merge Page — The redesigned Merge page did not carry over the logic that automatically pre-selects the oldest eligible case as the default primary. Cases are now fetched in ascending creation date order, ensuring the correct case is pre-selected. (v5.89)

Line Breaks Lost When Copying Child Case Descriptions as Comments — When child case descriptions were added as comments on the parent case during a merge, line breaks were stripped, and all content appeared as a single unformatted block of text. Line breaks are now preserved and rendered correctly in rich text. (v5.88)

"Failed to Get Access Token" Error With Migrated External Client Apps — Configuring the "Configure External Client App or Connected App" setting with an External Client App that had been migrated from a Connected App produced a "Failed to get access token: Consumer key and certificate name are required" error. The setting now correctly handles both standard and migrated External Client App configurations. (v5.87)

Child Objects Not Cloned or Reparented When "Object Cloning Selection" Is Disabled — When the "Object Cloning Selection" setting was disabled, no child objects were being cloned or reparented during a merge, even though all objects should have been processed. Child object handling is now correct regardless of whether this setting is enabled. (v5.86)

Duplicate Detector Displayed Incorrectly in Narrow Columns — The Duplicate Detector component rendered with elements out of bounds when placed in a narrow column on a page layout. The component now displays correctly at any column width. (v5.85)

"Apex Type Unsupported in JSON" Error in Setup Wizard — Configuring the "Configure External Client App or Connected App" setting triggered an "Apex Type unsupported in JSON: System.SelectOption" error, preventing the wizard from initializing correctly. The controller now uses the correct serializable type, resolving the error. (v5.85)