> 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/display/progress-bar.md).

# Progress Bar

Progress bar filling between configurable min and max, with optional percentage status text

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-8752e38e699b21dba307133658ea90956e551dd8%2Fwidget-progress-bar.png?alt=media" alt="Three progress bars showing how far three production orders are, one of them complete in green" width="608"><figcaption></figcaption></figure>

A progress bar fills between a minimum and a maximum and can show the percentage below. Link a count to it and set the maximum to the target, and users see how far an order, a batch or a shift has come. Your logic can change the bounds and the color on the fly, for example to green when an order is done.

**Good for:** order and batch progress, shift targets, uploads and long-running jobs.

## 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" %}
**`value`** (from an output, `number`): The current progress value (between the configured `min` and `max`).

<details>

<summary>Example</summary>

```json
67
```

</details>

**`min`** (from an output, `number`): Lower bound of the scale.

<details>

<summary>Example</summary>

```json
0
```

</details>

**`max`** (from an output, `number`): Upper bound of the scale.

<details>

<summary>Example</summary>

```json
200
```

</details>

**`showStatus`** (from an output, `boolean`): Show the percentage status text.

<details>

<summary>Example</summary>

```json
true
```

</details>

**`color`** (from an output, `string`): Any valid CSS color for the bar (overrides the configured color).

<details>

<summary>Example</summary>

```json
"#dc2828"
```

</details>

**`props`** (from an output, `object`): Facilitates setting several properties at once, e.g. `{ "min": 0, "max": 200, "showStatus": true, "color": "#dc2828" }`. The bundle wins over the individually linked channels.

<details>

<summary>Example</summary>

```json
{
  "min": 0,
  "max": 200,
  "showStatus": true
}
```

</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>Look &#x26; feel</summary>

* **Minimum**: Value at which the bar is empty (0%).
* **Maximum**: Value at which the bar is full (100%).
* **Show status**: Shows the percentage text next to the bar.
* **Bar width**: Thickness of the bar in px. Range 2 to 40. *Set per screen.*
* **Color**: Fill color of the bar; empty or auto keeps the theme's accent.

</details>


---

# 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/display/progress-bar.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.
