> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/system/change-log/version-1.0.176.md).

# Version 1.0.176

(published October 22, 2026)

#### New features

* Expanded the configuration of the DLP trigger for file move and copy operations to support the source drive type.
* Added the option to select all cloud applications at once when configuring the file upload trigger.

#### Improvements and technical changes

* Fixed replication of DLP rules that do not have a trigger defined.
* Sorted the lists of triggers and actions alphabetically in the DLP rule configuration forms.
* Bulk actions for DLP rules and archived rules are available only after at least two items are selected.
* Changed the height of the selection list in the configuration of the trigger for visited websites.
* Information about downloading pro forma invoices is now always visible in the payment settings.
* Improved notification handling so that repeated triggering of the same event does not cause multiple messages to appear at once.
* Sorted the list of device groups in the configuration of the device connection trigger.
* Implemented additional technical fixes to the handling of forms and DLP rule data.


---

# 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://eaclouddoc.eauditor.eu/eacloud-docs-en/system/change-log/version-1.0.176.md?ask=<question>&goal=<user_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.
