This release focuses on updates to Switchboard and the Follow-Up Process, plus performance and security improvements.

Switchboard renders in your org's configured brand colors, ensuring a consistent visual experience across your Salesforce environment.

To improve processing efficiency and reduce governor-limit consumption, triggers exit early when Case Flags is not enabled for a given case.

This release also includes security and performance improvements. If Case Flags data is not displayed as expected, check sharing rules, object permissions, and field-level security.

Switchboard No Longer Displays Console Errors on Hover — We removed event handlers that triggered console errors when users hovered over case numbers in Switchboard. (v6.80)

External Client App Missing — When an org had more than 10 External Client Apps, the setup wizard only displayed the first 10, preventing admins from selecting apps further down the list. (v6.79)

"Load More" Button Restored in Component for Case Flags History Tracking (v6.79)

Follow-Up Process Only Runs on Open Cases — Running the Follow-Up Process on closed cases could cause a loop where flags were repeatedly reset. (v6.79)

Sort Order for List Views and Reports Impacted by Salesforce's Spring '26 Release — Salesforce changed how null values are handled in sorting, causing unflagged cases to sort above flagged cases. Flag, Flag (BH), and Flag Sort formula fields have been modified to restore the expected sort order. (v6.78)

Follow-Up Process Compatible with Email to Case Premium Email Loop Protection — The Follow-Up field now populates correctly. (v6.77)

"Company Domain" Matching is Case Insensitive — Internal and external emails are correctly distinguished regardless of capitalization. (v6.76)

Case Compact Layout Assignment No Longer Resets on Follow-Up Process Deployment — A known Salesforce issue caused the org's assigned Case Compact Layout to reset to the system default when the Follow-Up process was deployed. (v6.75) 

Editing Custom Aging Speeds No Longer Fails — Deleting a Custom Aging Speed entry without saving first caused subsequent edits to other entries to fail until the page was saved or refreshed. (v6.74)

"Failed to Get Access Token" Error With Migrated External Client Apps — External Client Apps migrated from a Connected App no longer return an error.  (v6.74)