> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/de-documentation/produktaktualisierungen-on-premise/release-notes/2024/24.83.0-on-premise.md).
# 24.83.0 - On Premise
*Version 24.83*
*Enthält alle Änderungen seit Version 24.71*
**Neue Funktionen und Verbesserungen:**
RQ059230 - Set default status when copying items between projects or within project
RQ059269 - Capture | Mask password, username, credit card etc hidden when recording the video
RQ059833 - Test Execution | Display test description on the test execution page
RQ059980 - Statistics | New design for statistics page + enahncements
**Gelöste Fehler:**
DF059545 - Editor | Link | When providing the link in the editor it's not interpreted as a URL, but as a plain text
DF060120 - Home | The select agent button on the homepage leads to the same page
DF060176 - Reports | Path value is not exported to the Excel file, even though there's a value in the system
DF060190 - Test execution | Test scenario | Test case fields show same value for all test cases
---
# 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.aqua-cloud.io/documentation/de-documentation/produktaktualisierungen-on-premise/release-notes/2024/24.83.0-on-premise.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.