> 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/vordefinierte-widgets/digitaler-trend.md).

# Digital trend

A digital trend shows the change of a binary value over a certain period of time.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/zXMmyi4F6tW8RX4WZrpi/80AB7FF3-7E97-4AA0-A5B4-54DF80DC3168.png" alt=""><figcaption><p>A digital trend</p></figcaption></figure></div>

## When should this display be used?

The "Digital Trend" display should be used when you want to track the progression of a binary value over a certain period of time - e.g. the occupancy status of a parking space (occupied/not occupied).

## Overview

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/ZV4Nf0sLQysrrOoy2iyP/4DC65EDB-9416-4A47-94FE-62C054D9DB0A.png" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="86.33333333333331"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Title</td><td>Widget title. Influenced by the selection of the "Primary Asset" (see below.)</td></tr><tr><td><strong>[B]</strong></td><td>Icon</td><td>Widget icon</td></tr><tr><td><strong>[C]</strong></td><td>Name of the value trend</td><td>Can be adjusted when creating the widget.</td></tr><tr><td><strong>[D]</strong></td><td>Content</td><td>The digital trend of a value</td></tr><tr><td><strong>[E]</strong></td><td>Set scaling</td><td>Click to select whether a day, a week, or a month should be displayed.</td></tr><tr><td><strong>[F]</strong></td><td>More options</td><td></td></tr><tr><td><strong>[G]</strong></td><td>Value</td><td>Current value</td></tr></tbody></table>

## Configure digital trend

{% @supademo/embed url="<https://app.supademo.com/demo/E8NZiw52nUugHrMXPj-sL>" demoId="E8NZiw52nUugHrMXPj-sL" fullWidth="true" %}

1. Make sure you are in the “Dashboard” menu.
2. Click “Add widget”.
3. Click on "View"
4. Click on "Digital Trend."
5. Select the primary asset. The name of this asset will appear in the widget title bar.
6. Select the asset for which you want to create the Digital Trend.
7. Select the attribute for which you want to create a Digital Trend.
8. Optional: Choose the color in which the trend should be displayed
9. Optional: Adjust the label of the value. This label will be displayed in the widget under **\[C]** displayed
10. Choose whether the current value or the aggregated value should be displayed.
11. Optional: Repeat the last steps to create an analog trend for another asset. Both trends will then be overlaid in this widget.
12. Optional: Choose how much space your new widget should take up on the dashboard. By default, each widget takes up 1 column.
13. Click “Add widget”.

## Set scaling

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/959Fq1bNDIPsmMClUPmL/98A82270-E000-4569-A05E-A2952FCE248C.png" alt=""><figcaption><p>Hourly, weekly, or monthly display</p></figcaption></figure>

Click repeatedly on Set scaling **\[E]**, to select whether a day, a week, or a month should be displayed.


---

# 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/vordefinierte-widgets/digitaler-trend.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.