> 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/reporting/parametrization-of-reports.md). # Parametrization of reports In aqua, you can enter parameters to specialise and filter your reports. To do this, open the report designer. On the right-hand side, under 'Field List' tab, you can enter a new parameter for the report, which can be used to specify or filter elements. \ \ Let's see how to filter the tested version of a test execution in a test scenario :rocket:\ \ Select 'Parameter' from the field list and click on![](http://aquawiki.andagon.com/pictures/drex_parametrization_1_custom.png).

Now you can specify the parameter properties

For this example, we are going to specify our parameter as follows: **Name:** tested\_version **Type:** String Then we are goingg back in the Report Designer, now we are going to filter our band with the following data: "ReportData.TestScenarioReport.TestScenarios.Execution" by selecting the properties and click on the three dots next to filter string.

Select the field corresponding to the value of your parameter, select 'Contains' and choose 'Parameter' from the drop-down menu. Your parameter should now be visible.

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.aqua-cloud.io/documentation/reporting/parametrization-of-reports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.