> 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.13-monthly-release-notes.md). # Backup & Archive (v4.7.13) - Monthly Release Notes {% hint style="info" %} #### **Release Details - Backup & Archive - v4.7.13 - July 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) {% 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.13)**. This release gives you finer control over Archive and Restore jobs by selectively disabling automation, so only the processes you choose are paused during a job. It also lets you export data directly to external cloud storage such as AWS S3 and Azure Blob Storage through a new step-by-step wizard. Finally, metadata restores that include Apex components now support configurable test-execution modes and improved detection of deployment failures caused by test or code-coverage issues. ## ![](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) Selective Automation Process Disabling #### What Changed Previously, disabling an automation in Archive and Restore jobs turned off all automations of that type. You can now fine-tune which automation processes are disabled while a job runs. For example, instead of disabling all triggers, you can disable only specific ones. To disable an entire automation type, leave its individual automations unspecified. #### Why It Was Done Disabling all automation is often unnecessary and can affect unrelated business processes. Controlling which automations to disable minimizes these side effects while keeping the automation required for a safe job managed correctly during execution. #### What You Will Notice * The option to selectively disable specific automation processes during a job. * More control over automation behavior during data operations. * No changes required to existing workflows. * Safe fallback behavior when an automation configuration is missing or invalid. ## ![](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) Export to External Cloud Storage #### What Changed The export workflow now supports sending export data directly to tenant-configured AWS S3 or Azure Blob Storage (Global Settings > Storage). When creating an export, you now have the option to export to: * **Internal Storage**: exports remain within the application and can be downloaded later from the Exports page. * **External Storage**: exports are uploaded directly to configured cloud storage providers, such as AWS S3 or Azure Blob Storage. The export creation flow now uses a step-by-step wizard, letting you select the export destination and configure the storage path for external exports. #### Why It Was Done Previously, all exports were stored only in application storage and had to be downloaded from the Exports page. Storing exports directly in your own cloud environment provides more flexibility for customers who prefer to keep exported data in their own cloud storage, simplifies data management, and reduces dependency on application storage. #### What You Will Notice When creating a new export, you will see a Select Destination step where you can choose between **Internal Storage** and **External Storage**. When External Storage is selected, you can choose one of the cloud storage locations configured for your tenant and specify the destination path. The default export path is `flosum/exports`, and the selected destination and storage path also appear in the export details. Existing export functionality remains unchanged for users who continue to use Internal Storage. ## ![](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) Run Apex Tests During Metadata Restore #### What Changed The metadata restore process now lets you control how Apex tests run during deployment. When a restore includes Apex classes or triggers, you can select one of the following test execution modes: * **Run Specified Tests**: run specific test classes that you provide. * **Run Local Tests**: run all local tests in the organization. * **Run All Tests**: run all tests, including managed package tests. Test execution configuration is available only for metadata restores that include Apex classes or triggers. Deployment failure handling has also been improved to correctly detect deployments that fail due to test execution or code coverage issues. #### What You Will Notice When restoring metadata with Apex components, you will see a new **Test Execution Mode** option and can choose your strategy before starting the restore. Selecting **Run Specified Tests** lets you enter test class names manually, while **Run Local Tests** or **Run All Tests** apply broader test validation. --- # 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.13-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.