Case Flags Release Notes 6.55 - 6.62

  • Jul 2, 2025
  • Knowledge

Permalink
https://kb.vicasso.com/?kb=000005414
What's New
  • A new "Aging Speed" field was added to the Case Flags History Tracking object, identifying the aging speed of the case at the time the Case Flags History Tracking records are created. (6.58)

  • The page layout component was updated to remove the Case Flags title and repetitive use of the app's name in its tabs. (6.61)

 

Improvements
  • The logic formula now accepts operators in lower and upper case. (6.55)
  • When using "Business Hours," we display the batch job running user in the setup wizard. (6.55)

  • Case Flags is now compatible with Salesforce's ICU locale formats. (6.55)
  • Fields in the "Create Follow-Up Fields" drop-down menus are now displayed alphabetically. (6.55)
  • Updated setting placement for "Automated Users" to live under the Email to Case section of the Flag Event Rules tab of the setup wizard. (6.56)
  • Updated the description for "Exclude Comments With Company Domain" and ensured it's searchable in the setup wizard. (6.56)
  • Since having a blank "Next Steps" (or custom field) is not helpful to support agents, we now override it with the default text from the settings in the setup wizard after users manually blank it. (6.56)
  • We now ensure that no duplicate or packaged date/time fields can be added to the Case Flags Follow-Up Process, and that no fields are set when the process is disabled. (6.57)
  • Case Flags has been optimized for Salesforce's SLDS2 design updates. (6.58)
  • To make it easier to understand Case Flags History Tracking records, the "Action" field will now use the "Local Automation" value when flags are set/cleared via local automation, instead of using the "User Action or Non-Flags Automation" value that was too generic for these scenarios. (6.58)

  • Updated screenshots and graphics in the "Deliver the Best Experience" tab in the setup wizard to reflect SLDS2 updates. (6.61)
  • A new "Can Edit All Switchboard Views" custom permission was created and added to the Admin Permission Set to allow a user to edit a Switchboard view created by any other user. (6.61)
Bugs Fixed
  • Emails without full error messages that read "The Case Flags Batch Job has failed with the following error:" have been optimized and will only fire for Business Hours batch job failures. (6.55)
  • Fixed an issue where the flag icons in the Utility Bar Component and the field in the case page layout did not match. (6.56)
  • Fixed an issue causing the  "FLAGS.UpdateCaseFlagOnEmail: execution of AfterInsert caused by: System.QueryException: WHERE LinkedEntityId IN ('02scW000002woRl') ^ ERROR at Row:1:Column:101 duplicate field selected: FLAGS__Initial_Response__c (FLAGS)" error when sending emails on cases. This was observed when the "Initial Response" field is configured as the "Follow-Up On" field for the Case Flags Follow-Up Process. (6.57)
  • Fixed the issue where the FLAGS_METRICS__Business_Hours_Elapsed_Previous__c field in the Metrics Extension package was being populated with an inflated value if the PreviousBusinessHours__c field was blank at the time the business hours batch job ran during active business hours. (6.57)
  • We now ensure that the Utility Bar component successfully initiates every time, avoiding mismatched/broken flag icons from the main component in page layouts. (6.58)
  • Chatter triggers now respect organization-wide and selective processing of cases, and no longer run on every single case in the org, avoiding incorrectly setting the flags. (6.58)
  • Fixed an issue where the wrong Aging Speed would be assigned when multiple cases are updated in one transaction due to our caching mechanism. (6.59)
  • The component pop-up error "Error during LWC component connect phase: [Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.]" should no longer appear when loading the setup wizard. (6.60)

  • The job controlled by the "Automatically Clear Flags on Closed Cases in the Past" setting will no longer update cases that are not enabled for Case Flags. (6.60)
  • Fixed the "[this.checkFlowTriggersDeploymentStatus is not a function]" error popping up in the setup wizard when deploying the Follow-Up Process. (6.61)

  • Fixed the issue where the setup wizard would not load if the running user did not have the "Manage Certificates" permission, which is required to determine the Connected App's certificate expiration. (6.61)
  • The error " [Cannot read properties of undefined (reading 'includes')]" was resolved and no longer shows up when loading the setup wizard. (6.62)

 

Title
Case Flags Release Notes 6.55 - 6.62
URL Name
Case-Flags-Release-Notes-6-55-6-62