File Slayer Release Notes 4.15 - 4.25

  • Dec 3, 2025
  • Knowledge

Permalink
https://kb.vicasso.com/?kb=000005434
What's New
  • The app has been optimized to account for SLDS2 design updates. (4.16)
  • A new feature parameter was added to license records to control license enforcement. (4.15)
    • Unlicensed users will see the following message on record pages where the component was added:

    • Images owned by unlicensed users will not be eligible for slaying through the Hit List Manager:

    • Retroactive removal will not slay images owned by unlicensed users.
    • When files are added to Salesforce via API or Context Users, such as when processing inbound emails through email services, they will only be automatically slayed if that user is licensed.
Improvements
  • The setup wizard now notifies users of any unsaved changes. (4.15)
  • The "File Slayer" title was removed from the component. (4.16)
  • If the component attempts to delete a file that was already deleted, a warning message will be displayed. The already deleted file can be found in the "Recover Images" section of the component. (4.16)

  • A new hidden setting called "Slay In Queueable" was added, which can be enabled for customers who have local automation that calls a future method on file deletion. (4.25)
Bugs Fixed
  • Upgrading from versions prior to 3.50 to newer versions (4.0+) should no longer result in the "The post install script failed." error message. (4.15)
  • Fixed the error "icap:Too many query rows:50001" when slaying images from the component when more than 50K files exist on the Hit List. (4.15)
  • Fixed an issue with Vicasso's license enforcement mechanism to ensure that unlicensed user activity is properly logged. (4.17)
  • The component should no longer break and display the "A Component Error has occurred!" message if Lightning Web Security (LWS) is disabled in the org. (4.18)
  • Users should no longer see the "Name: There is already an item in this list with the name XYZIDNAME" in the Hit List Manager. (4.19)
  • Fixed the issue where images were not automatically slayed when processed by the email service's context users. (4.20)
  • Updated our packaged triggers' sharing to fix the error "Failed to invoke future method ‘private static void slayHitListFileslnFuture(Set<ld>)' on class ‘icatp.ContentDocumentLinkTriggerHandler’ for job id ‘jobidnumber' caused by: System.DML Exception: Delete failed. First exception on row 0 with id 069Pd00000UrdhvIAB; first error: INSUFFICIENT_ACCESS_OR_READONLY, insufficient access rights on object id: 0” that was being sent to users. (4.21)
  • Errors such as "CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY : icatp.ContentVersionTrigger: execution of AfterInsert caused by: System.DmlException: Delete failed. First exception on row 0 with id 069N300000hRWKqIAO; first error: ENTITY_IS_DELETED, entity is deleted: [] (icatp)" should no longer appear when the duplicate file deletion is happening. (4.22)
  • Fixed an issue in Winter '26 where the settings' descriptions in the setup wizard were all bolded in SLDS2. (4.23)
  • Updated the code to ensure that when slaying files through a Case Merge Premium merge via our cross-app integration feature, it only attempts to slay files related to the cases involved in the merge, rather than the entire organization, avoiding the "icatp:Too many DML rows: 10001 Error is in expression '{!csmerge}' in page csmrgp:csmrgselect: Class.icatp.SignatureSlayerExtension.slayFilesForCases: line 275, column 1." error (4.23)
  • Adjusted our code to avoid the "Collection size 1,067 exceeds maximum size of 1,000" error from showing up on the Hit List Manager. (4.24)
Title
File Slayer Release Notes 4.15 - 4.25
URL Name
File-Slayer-Release-Notes-4-15-4-25