> 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.171.md).

# Version 1.0.171

(published 08.10.2026)

#### New features

* Domain information has been made available.

#### Technical improvements and changes

* The button layout in the DLP rules summary has been improved.
* Rule restoration has been accelerated by performing operations in parallel.
* Server communication resilience has been improved - in the event of selected connection errors, the system automatically retries the request.
* A loading indicator has been added during initialization of the user profile form.
* User redirection has been improved when required permissions are missing.
* Information has been added that preliminary invoices cannot be downloaded.
* The appearance of inactive buttons and icons has been improved, increasing the readability of elements unavailable to the user.
* The setting of time ranges used in schedules has been improved.
* Loading and display of the automation rules edit view have been improved.
* Loading and display of the DLP rules edit view have been improved.


---

# 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.171.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.