> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets/benutzerdefinierte-widgets/module/trend.md). # Trend With the "Trend" module, you can display trends in a widget. The module provides extensive options for configuring trends.

The configuration options for the "Trend" module


[A]	Description	This text is displayed when the custom widget is later connected to assets.
[B]	Text	Free text
[C]	Type	Digital: Select the "Digital" type if you want to track the history of an asset that sends values between 0 and 1, e.g. a contact sensor. Analog: Select the "Analog" type if you want to track the history of an asset that sends values other than 0 and 1, especially floating-point numbers. This includes most assets that know states other than "On" and "Off", e.g. temperature sensors.
[D]	Variant	Choose whether the data should be displayed as a line chart, bar chart, or both.
[E]	Overlap	Possible options: Yes: all parameters are displayed in one line. No: each parameter is displayed in a separate line
[F]	Legend and values	Possible options: Yes: each parameter is explicitly displayed with its name and a numeric value. No: neither the value nor the title is displayed. Whether the Current Value or the Aggregated Value is displayed for a parameter can be selected when an asset is connected to the widget.
[G]	Target area	The details for the target area can be entered when the custom widget is later connected to assets.
[H]	Y-axis label	Indicates whether a label should be displayed on the Y-axis.
[i]	Multiple axes	Should only be enabled when: "Overlap" is set to "Yes" "Y-axis label" is set to "Min, Average, Max"

--- # 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.buildings.ability.abb/collection/english-v14/documentation/widgets/benutzerdefinierte-widgets/module/trend.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.