> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/reference/widgets/layout/group.md).

# Group

Holds other widgets as one unit and repeats them as one tile per data row, binding row fields to member properties by member name; formed from placed widgets (group\_widgets in the tools, Group in the

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-5f2e39a1d4231fdfae08756b7bd5e1ba7b198b9e%2Fwidget-group.png?alt=media" alt="A group repeated as four machine tiles, each with a name, a status lamp, the current speed and a sparkline of the last hour" width="1048"><figcaption></figcaption></figure>

A group holds several widgets as one unit, and it is the platform's repeater: link a list to it and it draws one tile per row. You design one tile, for example a card with a name, a status lamp, a value and a sparkline, and map the row's fields to its widgets. Four machines give four tiles, forty give forty, with no extra work. Clicks and inputs inside a tile come back to your logic together with that tile's row.

**Good for:** machine and station overviews, order and job cards, any list that deserves more than a table row.

## Properties

The widget's General tab lists these properties under Receives and Emits. Drop an executor's output, input or trigger onto a row to link it. An example also fills an unlinked widget as demo data in the App Builder.

{% tabs %}
{% tab title="Receives" %}
**`data`** (from an output, `Array<object> | object`): The rows to render: one tile (with the full set of child widgets) per row. A single object becomes one tile; the binding editor maps row fields to child properties. A row field may itself hold an **array of points** — bind it to a chart, sparkline or timeline child.

<details>

<summary>Example</summary>

```json
[
  {
    "name": "Pump A",
    "pressure": 2.4,
    "running": true,
    "status": "running",
    "history": [
      {
        "timestamp": "2026-08-12T10:00:00Z",
        "pressure": 2.2
      },
      {
        "timestamp": "2026-08-12T10:05:00Z",
        "pressure": 2.6
      },
      {
        "timestamp": "2026-08-12T10:10:00Z",
        "pressure": 2.4
      }
    ]
  },
  {
    "name": "Pump B",
    "pressure": 3.1,
    "running": false,
    "status": "idle",
    "history": [
      {
        "timestamp": "2026-08-12T10:00:00Z",
        "pressure": 3.4
      },
      {
        "timestamp": "2026-08-12T10:05:00Z",
        "pressure": 3
      },
      {
        "timestamp": "2026-08-12T10:10:00Z",
        "pressure": 2.9
      }
    ]
  }
]
```

</details>
{% endtab %}

{% tab title="Emits" %}
**`onChange`** (into an input, `object`): Writes the tile's row augmented with the changed child value whenever an input child changes.

<details>

<summary>Example</summary>

```json
{
  "index": 0,
  "name": "Pump A",
  "pressure": 2.4,
  "form1": {
    "value": 42
  }
}
```

</details>

**`onButtonClick`** (into an input, `object`): Writes an event envelope when a button child is clicked. Pending child input values of the same tile are merged in.

<details>

<summary>Example</summary>

```json
{
  "index": 0,
  "clickedBy": "button1",
  "buttonText": "Go",
  "name": "Pump A",
  "pressure": 2.4
}
```

</details>

**`onGroupClick`** (into an input, `object`): Writes the tile's row (plus pending child input values) when the tile is clicked.

<details>

<summary>Example</summary>

```json
{
  "index": 0,
  "name": "Pump A",
  "pressure": 2.4
}
```

</details>
{% endtab %}
{% endtabs %}

## Settings

Double-click the widget in the Page editor to open its settings, grouped in these tabs. Settings marked *set per screen* are pinned by nature: every screen keeps its own value.

<details>

<summary>Data binding</summary>

* **Member bindings**: Per member (by id), the row fields that feed its properties; set through the binding editor or set\_group\_bindings.

</details>

<details>

<summary>Look &#x26; feel</summary>

* **Horizontal axis**: How the tiles line up left to right.
  * **Justification**: Where the tiles of a row sit across the width; left, center and right keep the spacing, the space variants spread the tiles over the width. Choices: Left, Center, Right, Space between, Space around, Space evenly. *Set per screen.*
  * **Spacing**: Margin in px on both sides of every tile, so neighbours sit twice this apart. Range 0 to 80. Only when Justification is Left, Center or Right.
* **Vertical axis**: How the rows of tiles stack top to bottom.
  * **Justification**: Where the rows of tiles sit down the height; top, center and bottom keep the spacing, the space variants spread the rows over the height. Choices: Top, Center, Bottom, Space between, Space around, Space evenly. *Set per screen.*
  * **Spacing**: Margin in px below every tile. Range 0 to 80. Only when Justification is Top, Center or Bottom.

</details>

## Good to know

* It holds other widgets and repeats them, one tile per data row.


---

# 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.heisenware.com/reference/widgets/layout/group.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.
