> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.7.10-monthly-release-notes.md). # Backup & Archive (v4.7.10) - Monthly Release Notes {% hint style="info" %} #### **Release Details - Backup & Archive - v4.7.10 - July 9, 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) {% endhint %} ## ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FPL2eaOdTi7VscAjFymsv%2FSummary2-Small-Icon.svg?alt=media\&token=a14ffcd6-66df-43ec-aafc-61364d19c7cd) Summary This article documents the monthly release for **Backup & Archive (v4.7.10)**. This release focuses on a cleaner related records experience, more reliable package installation, and greater flexibility in how data is recovered and archived. It introduces Point-in-Time Restore for precise, time-based recovery and extends archive support to Salesforce records already archived in Salesforce. Existing backup, archive, and restore workflows remain unchanged. ## ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) Point-in-Time Restore A new Point-in-Time Restore option lets users restore Salesforce data to a specific date and time without manually identifying the backup or archive job that contains the required records. Instead of locating the correct backup job after accidental updates or deletions, users recover data from a specific point in time. The application automatically retrieves the data changes between the selected restore point and the current state. Before starting, users can review the records added, changed, deleted, or archived since that point, and then restore only the records they need. They can also apply filters, choose which fields to restore, and optionally disable automations before running the restore to achieve more precise and flexible recovery. ## ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FFX1KImFkBpbzYgGoBLl6%2FEnhance-Icon-Small.svg?alt=media\&token=6211adf4-19a2-458d-92fc-54b77a2a635a) Improved Related Records Experience in Salesforce Package Viewing related records is now cleaner and more focused. Previously, users could see numerous related object sections with no data, making it harder to locate the information that mattered. Related records are now displayed only for objects that actually contain data. This change streamlines navigation and keeps the interface focused on relevant information. You benefit from cleaner related record views without unnecessary empty sections, faster access to the details you need, and a more streamlined experience when working with records that have many relationships. ## ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FFX1KImFkBpbzYgGoBLl6%2FEnhance-Icon-Small.svg?alt=media\&token=6211adf4-19a2-458d-92fc-54b77a2a635a) Improved Salesforce Package Installation The installation process for the Backup & Archive Salesforce Package now compiles only the Apex classes that belong to the package being installed. Previously, installation triggered compilation of every Apex class in the Salesforce org, which could cause installations to fail when unrelated classes contained compilation errors. By limiting compilation to package components, installations are faster and more reliable and are no longer affected by unrelated customizations in the org. Administrators installing or updating the package will experience quicker installs and fewer failures, with no changes to the existing installation workflow. ## ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FFX1KImFkBpbzYgGoBLl6%2FEnhance-Icon-Small.svg?alt=media\&token=6211adf4-19a2-458d-92fc-54b77a2a635a) Support Archiving of Archived Salesforce Records Archive operations now include Salesforce records that have already been archived, such as Case and Task records. Previously, these records could not be archived, which meant archived Salesforce data could be excluded from backup and archive processes. This update ensures those records are fully supported. Archived Salesforce records are now handled the same way as regular records during archive operations: they are included in archive jobs, stored securely, and can be restored when needed. As a result, archived Case, Task, and other supported records now appear in archive results and can be successfully restored from backups. No changes are required to existing archive workflows, and the behavior for active Salesforce records remains unchanged. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.7.10-monthly-release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.