> 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/desktop-client/reporting/creating-a-new-report-template.md).

# Creating a new report template

Create custom report templates in the desktop client. Learn step-by-step how to build, modify, and manage new report templates for efficient, tailored data reporting.

To create a new report, it is important to decide which data you want to use as a basis. You can decide to base your report on requirements, test cases, test scenarios, or defects. The layout designer will not be affected by your choice, only the information displayed after creating the report will be compromised. It makes sense to specify the required data basis as precise as possible in order to avoid loading too much data that is not required in your report.

 

<figure><img src="http://aquawiki.andagon.com/pictures/drex_creating_a_new_report_template_2_custom.png" alt=""><figcaption></figcaption></figure>

&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_creating_a_new_report_template_2_custom_2.png" alt=""><figcaption></figcaption></figure>

&#x20;&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_creating_a_new_report_template_2_custom_3.png" alt=""><figcaption></figcaption></figure>

Following the completion of these steps, the blank layout designer will be opened. If this template is saved now, the report can be created with the Show Report button.


---

# 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/desktop-client/reporting/creating-a-new-report-template.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.