Appearance
Alarm Banner
The newest unacknowledged alarm with its Acknowledge button and a "+N more" count, for the top or bottom of every screen.
In Studio
In Studio, double-click Alarm Banner in the Components category of the Components panel. It is added to the open view, where you can drag it into place.
When to use
Use Alarm Banner in a header or footer dock so an operator always sees the alarm that needs them, without opening the Alarm Table. Pick filled for the strongest look (priority 1 only by default) and counts for a header that shows totals per priority.
Properties
| Property | Type | Default | Description |
|---|---|---|---|
| Style | outline, filled, counts | outline | How it looks: outline (default, the ring takes the priority color), filled (filled in the priority color, for priorities up to Filled Up To) or counts (per-priority totals plus the newest alarm's text). |
| Filled Up To Priority | 1, 2, 3, 4 | 1 | The filled style applies to priorities 1 up to this one (default 1). Lower priorities fall back to the outline. |
| Source Filter | String | (none) | Only alarms whose tag is in this folder or below. Accepts {view.params.X} and {page.params.X}. Set but empty or unresolved shows nothing; blank shows every alarm. |
| Ack Button Text | String | Acknowledge | The text on the Acknowledge button. |
| Text When Clear | String | No unacknowledged alarms | What the banner says when nothing is unacknowledged. |
Binding
This component has no single value binding.
Acknowledge uses the same endpoint and permission as the Alarm Table: it is not offered on a read-only page, nor to an anonymous session unless the project allows anonymous acknowledge, and the gateway still enforces the role. A failed alarm fetch reads "Alarms unavailable", never "no alarms". In the designer the banner draws a sample alarm set so the style can be seen.