Case Flags Release Notes 6.30 - 6.37

  • Dec 7, 2023
  • Knowledge

Permalink
https://kb.vicasso.com/?kb=000005301
What's New
  • Added field Aging Speed (FLAGS__Aging_Speed__c) that will populate the custom aging speed that is being used at present. If updates are made and the custom aging speed is changed in the duration of the case, this field will re-calculate on refresh. [Change 00212454] (6.33)
  • Switchboard video is now available through a question mark button within the Switchboard View and when creating a new view. [Change 00212751] (6.34) 
Improvements
  • Improved error handling for deleted fields and jobs for Case Flags. [Change 00212126] (6.30)
  • Add an "Automatically Clear Follow-Up Fields on Case Closure" setting to the Case Flags Set Up. [Change 00212360] (6.31) 
  • Follow-up process queries in Util.cls are now cached to further reduce SOQL usage. Additionally, rare edge case is now handled in previous business hours calculation. [Change 00212383] (6.32)
  • Improved the "Next Steps" field behavior to check the initial text before setting it to the subsequent text. [Change 00212403] (6.32) 
  • Improved language throughout the Case Flags Set Up. [Change 00212400] (6.32) 
  • Improved the Case Flags Aura record page component and the Utility bar component with some optimizations to improve performance and prevent increased logs from flooding the Developer Console. [Change 00212178] (6.32) 
  • Improved language with the Setup Wizard. [Change 00212399] (6.33) 
  • Improved Follow-up and next steps field behavior. [Change 00212402] (6.33) 
  • The follow-up process will now dynamically update the follow-up on and next steps fields if a case is changing between aging speeds [Change 00212515] (6.33) 
  • The invocable method used by the follow-up flow will now check that the org is either in org-wide mode or that the case is enabled for case flags before updating. [Change 00212731] (6.33) 
  • Updated the Action on the History Tracking Record to "Follow-Up Process" if the Flag was set with the Follow-Up Process. [Change 00212823] (6.34) 
  • Updated text in Follow-Up Process tab. [Change 00212971] (6.35)
Bugs Fixed
  • Fixed an issue where follow-up fields were being overridden on flag clear, we added checks to avoid overriding existing values. [Change 00212360] (6.31) 
  • Fixed an issue where Tests were not flagged to run during deployment causing issues during deployment. [Change 00212350] (6.31)
  • Fixed a typo that was preventing an error related to the history tracking cleanup job from displaying to the end user. [Change 00212290] (6.31)
  • Resolved a bug where cases where the follow-up fields were not being cleared on case closure. [Change 00212684] (6.33) 
  • Resolved an error that was occurring in the Setup Wizard for orgs without LWS enabled. [Change 00212871] (6.34) 
  • Resolved a bug where the next steps field was being overridden when a case was initially created. [Change 00212868] (6.34) 
  • Resolved an error that occurred when attempting to deploy the follow-up process flow by adding the missing namespace. [Change 00213035] (6.35)
  • Increased Business Hours support from 1,000 records to 5,000. [Change 00213143] (6.36)
  • The Case Flags Utility Bar component will no longer incorrectly show the wrong flag when initially loaded on a case using business hours. [Change 00213275] (6.37)
  • The initial response is now respected in custom aging criteria [Change 00212144] (6.37)
Title
Case Flags Release Notes 6.30 - 6.37
URL Name
Case-Flags-Release-Notes-6-30-6-37