> 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/einfache-anzeige.md).

# Simple display

The "Simple Display" widget shows a value for one or more assets.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/p11LWb5zVgYDNzdK4Gsl/5426E1F4-C06B-42FD-B775-C920F8EECA73.png" alt=""><figcaption><p>The "Simple Display" widget with 2 linked assets</p></figcaption></figure></div>

## Overview

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/p2gXfVgZeO0TKaIkOeKr/D3F9B453-476E-4282-9CE0-987DACB36848.png" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="102.33333333333331"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Title</td><td>Widget title. Affected by the selection of the "Primary Asset"</td></tr><tr><td><strong>[B]</strong></td><td>Icon</td><td>Widget icon</td></tr><tr><td><strong>[C]</strong></td><td>Value</td><td>Value of the selected attribute</td></tr><tr><td><strong>[D]</strong></td><td>Name of the attribute</td><td>Can be set under <strong>[H]</strong> set</td></tr><tr><td><strong>[E]</strong></td><td>More options</td><td>See -> Navigating through widgets</td></tr></tbody></table>

## Configuration

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/q7H6IYboDao81WAr1O3O/8CD574B4-F9D1-43D3-B36E-1762D1B346E0.png" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="121.33333333333331"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>[F]</strong></td><td>Primary asset</td><td>Select primary asset. This selection determines which title <strong>[A]</strong> appears in the widget</td></tr><tr><td><strong>[G]</strong></td><td>Attribute</td><td>The attribute whose value is displayed in the widget</td></tr><tr><td><strong>[H]</strong></td><td>Name of the attribute</td><td>Displayed in the widget <strong>[D]</strong></td></tr><tr><td><strong>[I]</strong></td><td>Current value/Aggregated value</td><td>Select whether the current value or an aggregated value should be displayed.</td></tr><tr><td><strong>[J]</strong></td><td>Add more assets</td><td>Add more assets</td></tr><tr><td><strong>[K]</strong></td><td>Add widget</td><td>Save inputs and add widget</td></tr><tr><td><strong>[L]</strong></td><td>Width</td><td>Select how much space the widget should take up on the dashboard.</td></tr></tbody></table>


---

# 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/einfache-anzeige.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.