Skip to content
Version 2026.25

Alarm Table ​

A live table of active alarms, or a historical alarm journal.

In Studio ​

In Studio, double-click Alarm Table 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 Table on an overview or alarm-summary screen. Set Show Journal to review acknowledged/historical alarm activity rather than the current active list.

Properties ​

PropertyTypeDefaultDescription
TitleStringActive AlarmsThe header text. Defaults to "Active Alarms" or "Journal" depending on Show Journal when left blank.
Show Journalfalse, truefalseFalse (default) shows currently active alarms, with an Ack action per row. True shows the alarm journal (historical events) instead, with no Ack column.
Filter Stateall, unacknowledged, acknowledgedallRestricts the active-alarm list to all, unacknowledged, or acknowledged rows. Has no effect when Show Journal is true.
Max RowsNumber100The maximum number of rows fetched and shown.
Refresh (s)Number10The polling interval in seconds, used only as a fallback while the table's live WebSocket feed is not connected — once connected, updates arrive immediately and polling drops to a slow 60-second background check. The fallback polling rate is clamped to at most every 10 seconds regardless of what is entered.
Source FilterString(none)A tag folder. Only alarms whose source tag is that folder or under it are shown, e.g. one device's alarms on its popup. Accepts {view.params.X} and {page.params.X}. Blank = no filter; set but empty or unresolved shows no rows.
Show Ack Allfalse, truefalseTrue adds an Ack All button that acknowledges every alarm the table is showing (after its filters).
Allow Shelvingtrue, falsetrueTrue lets a signed-in operator shelve an active alarm: a Shelve button on each row asks for a reason and a time. Everyone sees a "N shelved" count that opens the shelved list, where a signed-in operator can unshelve. False hides the buttons, the count and the list. Not used in journal mode.
Shelve Choices (min)String15,60,240,480The minutes offered in the Shelve picker, comma-separated, each from 1 to 1440. Anything else falls back to the default.
Densityauto, comfortable, compact, touchautoRow spacing: auto (default), comfortable or compact. auto is comfortable in a Daylight project and the classic tight rows otherwise.
Rows per pageNumber0Rows per page. 0 (default) shows every row at once; a positive number shows that many with Prev and Next buttons, for touch panels where scrolling is a poor fit.
Surface ColorColor#E8E8E8The card behind the table and its header row (a fill set on the component's own style wins). The standard look has no card fill, so it appears once you set this; the Daylight card always has one. It applies at every density. Every color of the table is a property with one built-in default; set it to a color, or to a var(--name) that a style class defines. The priority shapes and state chips keep the locked alarm colors.
Text ColorColor#333333The text of the title, the Tag and Message cells and the pager buttons.
Dim Text ColorColor#666666Quieter text: the column headings, the counter, the time and page count, and the empty and loading messages.
Border ColorColor#B0B0B0The lines between the header, the rows and the pager, and the pager buttons' border.
Pager Button ColorColor#E0E0E0The Prev and Next button face.
Pager Text ColorColor#333333The text on the Prev and Next buttons.
Quality Markstandard, dimstandardHow a lost link is marked when a value this component shows has Stale or Bad quality. standard (the default) draws the quality outline and glyph over the value. dim keeps the last good value on screen, faded, with nothing drawn over it: it suits a dense panel where one lost link turns a whole column Bad. The value still reads as not live, and a binding that fails to evaluate keeps its outline either way.

Binding ​

This component has no single value binding.

No value binding — the table fetches its own data from the alarm API and a live WebSocket feed. Acknowledging a row (when Show Journal is false) posts an acknowledgment, which counts as a write action on the underlying alarm, not a tag write.

Shelving ​

Shelving silences one active alarm for a set time, with a reason. A shelved alarm keeps evaluating, but it leaves the active list and the alarm counts, and it starts no notification. Shelving needs the same permission as acknowledging, and a signed-in session: the gateway journals who shelved it, why, and for how long. The shelf ends when its time runs out, or when an operator unshelves it from the shelved list; an alarm that is still active and unacknowledged then returns to the list and notifies again. An alarm that clears and trips again while shelved stays quiet until the shelf ends. A restart of the gateway keeps shelves and their end times.

Scripts and Iris read the same active list, so they do not see a shelved alarm either, as with Ignition's alarm status query. Its reason and who shelved it are shown wherever the alarm's acknowledgment details are, including to an anonymous kiosk that can see the alarm.