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

# Version 1.0.167

(published 18.09.2026)

**Improvements and technical changes**

* Dictionary entries were sorted alphabetically.
* The operation of switches in tables was improved, including proper updating of their values.
* Verification of key availability for the disk was improved.
* Selected descriptions in the interface were updated to better match the presented features.
* Error 400 handling was improved - the system now displays a separate message indicating invalid request data.
* The readability of port labels in the firewall configuration was improved.
* The link to the English eAgenta installation guide was corrected.
* The “Relations” tab was hidden in the computers view.
* The display of date and time in date picker fields was improved so that the full value is visible.
* The appearance and layout of charts in the system were standardized.


---

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