> 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/element-properties.md).
# Element properties
Customize element properties in aqua reports - adjust appearance, set event-driven scripts like 'Before Print', and manage report logic efficiently. SaaS editing requires the desktop client.
Each element in an aqua report has a set of properties that determine its appearance and the actions taken when the element fires an event.
An event triggered by an element can be, for example, 'Before Print', 'After Print', 'Changed Size' or 'Changed Text'. You can define a script function to be executed when such an event is triggered. For example, on a 'Before Print' event, you can change the text of the label, which is useful if a label is being printed within an iteration band.
Accessing the events settings
Changing the appearance of an element is straightforward. For example, the background colour can be set using the Background Colour parameter in the Appearance menu, or the font size can be changed using the Size parameter in the Appearance - Font menu.
{% hint style="info" %}
For users in a SaaS environment: Please note that the report script can only be managed from the desktop client.
The information on how to enable scripting mode for the On-Premise customers can be found in this [article](/documentation/installation-for-on-premise/server-parameters.md).
{% endhint %}
---
# 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/reporting/element-properties.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.
