Backup & Archive (v4.5.6) - Monthly Release Notes

Release Details - Backup & Archive - v4.5.6 - January 28th, 2026

This article is intended for Salesforce administrators, compliance officers, and IT teams responsible for managing Salesforce backups and data governance.

Release Type

• Monthly
• Applies to Flosum-hosted and self-hosted

Prerequisites

• Backup & Archive tenant setup
• Appropriate Flosum user permissions (SystemAdministrator or equivalent)

Summary

This article documents the patch release for Backup & Archive (v4.5.6). This release adds support for self-hosting the Backup & Archive app, the Add all dependents toggle, and several bug fixes.

License Manager Support for Self-Hosted Backup & Archive

Support for License Manager is now available for the self-hosted Backup & Archive app.

• The Global Settings app now shows an ENTER LICENSE KEY button for customer-hosted Backup & Archive deployments.
• Entering a valid license key provided by the Flosum team grants access to the cloud app.

Add All Dependent Toggle for Archive Templates

Included an “Add all dependents" toggle in the Child Objects popup for archive templates.

• This toggle allows you to quickly add all child objects that are automatically deleted when the parent record is deleted.
• When enabled, all child objects marked as Dependent are automatically selected, eliminating the need to add each dependent object individually.

Bug Fixes

• Fixed an issue in Archive Jobs where the job failed with the error: “Data too long for column 'recursive_chain' at row 1.”
• Resolved an issue on pages with tables and a Full Screen button where entering text containing the letter “F” incorrectly triggered full-screen mode.
• Corrected label typos:

  • Archive Template → Add Child Objects pop-up: Replaced “Depended” with “Dependent”
  • Restore Archive → Select Object step → Add Child Object pop-up: Replaced “Depended” with “Dependent”
• Fixed an incorrect toast message displayed when deleting a template. This was caused by an unnecessary backend request for scheduler details, which has been removed.
• Fixed an issue where switching organizations from the Search page retained object selections from the previous org, requiring a page reload.
• Resolved an error encountered during restore jobs: “FieldDefinition does not support queryMore() in restore request.”