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

Release Details - Backup & Archive - v4.7.21 - August 20, 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

• A registered and configured Flosum Cloud Apps tenant
• Appropriate Flosum user permissions (SystemAdministrator or equivalent)

Summary

This article documents the monthly release for Backup & Archive (v4.7.21). This release redesigns how Backup & Archive retrieves Salesforce object metadata, reducing the overhead of describe calls and speeding up template creation, search, export, and restore operations. It also adds dependency validation to File-Based Archive, so an archive stops before the deletion phase when required file records cannot be archived. Together, these changes improve performance in large Salesforce organizations and protect against partial archives that leave orphaned files behind.

Faster Object Metadata Retrieval

What Changed

The logic for retrieving Salesforce object metadata has been redesigned and optimized. Describe calls are now processed more efficiently across several Backup & Archive operations, including:

• Backup Template creation
• Archive Template creation
• Search creation
• Export operations
• Restore operations

The updated logic reduces the number of unnecessary describe calls and improves the processing of the returned metadata.

Why It Was Done

Backup & Archive uses Salesforce describe calls to retrieve the field lists and object properties that many of its operations depend on. Previously, these calls could add unnecessary overhead and lengthen response times, especially in organizations with a large number of objects and complex metadata configurations. The new implementation reduces that overhead and improves overall performance.

What You Will Notice

You should experience faster response times when working with Backup Templates, Archive Templates, Search creation, Export operations, and Restore operations. The improvement is most noticeable in larger Salesforce organizations, where a single operation can require describe calls for a significant number of objects.

Dependency Validation for File-Based Archives

What Changed

File-Based Archive (FBA) now validates the required file-related dependencies before it starts the deletion phase of an archive operation. This prevents cases where some file-related records are archived successfully while dependent records cannot be, which could previously leave a partial archive.

Why It Was Done

Salesforce files rely on relationships between multiple objects, including ContentDocument, ContentDocumentLink, and ContentVersion. Previously, if records were archived without including all of the required dependent records, FBA could begin deleting data before all file relationships were processed. That could remove some records while leaving others behind, resulting in orphaned files and broken relationships. Validating file dependencies before deletion begins helps maintain a consistent archive state.

What You Will Notice

You will no longer be left with partially processed file archives when required file-related records cannot be archived. If the dependencies cannot be processed, the archive operation fails before deletion, preventing the Salesforce organization from being left in an inconsistent state. File relationships stay intact, which supports reliable restore operations and prevents orphaned ContentDocument records.