> 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.8.0-monthly-release-notes.md).
# Backup & Archive (v4.8.0) - Monthly Release Notes
{% hint style="info" %}
#### Release Details - Backup & Archive - v4.8.0 - September 17, 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 %}
##  Summary
This article documents the monthly release for **Backup & Archive (v4.8.0)**. This release adds AI agent filtering to the Backup and Restore workflows, so you can isolate, review, and restore only the records that AI agents created, updated, or deleted. It also extends archiving to EmailMessage records related to Tasks, which Salesforce does not expose as a standard parent-child relationship. Together, both changes give you finer control over which records you archive and which ones you bring back.
###  AI Agent Filtering
#### What Changed
The Backup and Restore workflows now support filtering data modified by AI agents. With the AI agent filter applied, you can:
* Filter objects to those that contain records created, updated, or deleted by an AI agent.
* View Created, Updated, and Deleted statistics limited to AI-modified records.
* Identify whether a record was modified by an AI agent.
* See a readable modifier, such as AI Agent or the configured agent name, instead of a Salesforce User ID.
* Restore only the records that were modified by AI agents.
The filtering is available in both the Backup workflow and the Restore workflow.
#### Why It Was Done
AI agents increasingly perform actions in Salesforce organizations, and those changes need to be distinguishable from changes made by regular users. Isolating them makes it easier to investigate what an agent did, understand the impact, and selectively restore the data it affected.
#### What You Will Notice
With the AI agent filter applied, the object list shows only the objects that contain AI-modified records, and the Created, Updated, and Deleted statistics count only those records. Records modified by an AI agent are marked as such, and the modifier appears in readable form rather than as a Salesforce User ID. The same filtering is available when you select records to restore.
Without the filter applied, Backup and Restore work exactly as they did before.
###  Improved Task and EmailMessage Archiving
#### What Changed
Archive now supports EmailMessage records related to Tasks, including the cases where Salesforce does not expose a standard traversable relationship between the two objects. You can:
* Select EmailMessage as a related child object when you create an archival rule for Task.
* Archive EmailMessage records together with their related Tasks.
* Restore EmailMessage records and their associated Task data correctly.
* Preserve editable Task information without creating duplicate email activity Tasks during a restore.
#### Why It Was Done
Salesforce manages the relationship between EmailMessage and Task differently from a standard parent-child relationship. This previously prevented EmailMessage records from being selected as child objects in Task archival rules, and it could make the related data difficult to restore correctly. The new implementation handles the Salesforce-specific relationship while preserving the existing behavior for standard object relationships.
#### What You Will Notice
EmailMessage now appears as a selectable child object when you build an archival rule for Task, so you can archive email activity data together with the Tasks it belongs to. Restoring that data returns both the EmailMessage records and their Task data without creating duplicate activity records, and the supported Task fields associated with the restored email activities are preserved.
Archive and Restore workflows for other object relationships continue to work as before.
---
# 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.8.0-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.
