File Slayer Release Notes 3.51 - 4.14

  • Jul 3, 2025
  • Knowledge

Permalink
https://kb.vicasso.com/?kb=000005413
What's New
  • The 100 KB size limit for image files and the 500 KB size limit for all other file types have been removed from the package. However, if using Attachments, the 100 KB size limit for the Hit List Manager remains. While there is no size limit, Salesforce's maximum allowed file size is 2 GB. Please note that searching across a wide date range or a large number of files within your organization may result in slower performance or errors. (3.53 - 4.2)
  • File Slayer has switched from storing the hash code of an image to a checksum in order to accommodate the larger file sizes. When upgrading to the latest version, a post-install script will run to convert existing hash codes into the Salesforce-standard checksum values. If that fails during upgrade, you may manually run it from the "Convert Hashcode to Checksum" setting in the wizard. This setting will not appear if the conversion was successful during the upgrade process. (3.57 - 4.2)

Improvements
  • File Slayer is now compatible with Salesforce's ICU locale formats. (3.51)
  • To avoid confusion when "Enable Retroactive Removal" is on, the component will only display the number of files found on the current record being viewed instead of displaying the number of files found in the entire org. (4.12)
Bugs Fixed
  • Fixed an issue in the setup wizard where settings with toggle controls could be toggled on/off if clicking outside the switch. (3.51)
  • Fixed an issue where Slaybot only slayed one copy of the same image if multiple existed on the same record. (3.52)
  • Fixed issues related to the Checksum conversion and various redundant texts in the setup wizard. (4.11)
  • Slaybot now correctly slays images that exist on other records when "Enable Retroactive Removal" is turned on. (4.12)
  • The "Manual Slaying" calculations for the Storage Saver are now taking into account duplicate and retroactive counts. (4.13)
  • Removed unnecessary access checks from the "SlayerObjectSettings__c" custom setting to avoid errors such as "An error occurred when inserting file Developer Console 2025-05-05 at 12.10.56 PM: [CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY] icatp.ContentVersionTrigger: execution of AfterInsert caused by: icatp.Util.FileSlayerException: Missing read permission for SObject Slayer Object Settings(icatp__). (icatp). Please check.” when processing files in inbound messages. (4.13)
  • Fixed null pointer exception errors when using the Case Merge Premium integration to slay files during merge processes. (4.14)
Title
File Slayer Release Notes 3.51 - 4.14
URL Name
File-Slayer-Release-Notes-3-51-4-14