The Alarm Grid is a CygNet-aware control that supports the creation of customizable and interactive tables for the display and management of large amounts of alarm data in columns and rows. Five customizable column types are supported: Alarm, Facility, Generic, Point, and a column displaying an alarm icon, which can be customized based on alarm priority for unacknowledged alarms. Alarm columns are mapped to an alarm attribute; facility columns are mapped to a facility attribute; generic columns can display any kind of scripted data of your choice and its cells can be edited in run mode; and point columns are mapped to point attribute. Point columns also support grid row summaries. Several other configurable properties are supported, including:
- Custom alarm filters that apply to the whole grid can be configured to limit grid data.
- A toolbar containing dynamic filters to limit data in run mode can be added to the top of the Alarm Grid. You can select multiple filters to limit the data in different ways.
- The Alarm Grid can be configured as a SiteService or facility receiver so that you can indicate where the Alarm Grid is receiving its data. Data can be sourced either from a SiteService (received from the screen or the Common Alarm Service (CAS)) or from facilities (received from the screen or from another control on the screen).The grid can be configured as a facility sender, responding differently when a row is clicked. It can send facilities from grid to grid, from a grid to other controls or your current screen, or from a grid to other controls on a different hyperlinked screen.
- This control supports hyperlinking to other screens via configuration or scripting. A single click or double-click action will send any configured facility to the receiving screen. Hyperlink supports the following operational modes: Open, Modal open (a subordinate popup window), Open and close, Replace, Replace with navigation, and Close.
- Cell background color, text color, and border color can be set to one of the following options: a) sourced from the colors configured in the CygNet point scheme for single color, foreground color, or background color, b) automatically follow the selected application theme regardless of the underlying color palette used, or c) be explicitly configured.
- Header background color, header text color, and grid background color can be set to one of the following options: a) automatically follow the selected application theme regardless of the underlying color palette used, or b) be explicitly configured.
- Colors displayed in the control can be overridden when a custom color palette is selected for the screen.
- You can configure whether to display alarm acknowledgment as a blinking cell background, blinking text, or blinking border when a point is in alarm.
- In the Canvas Native view a context menu is available in run mode to facilitate alarm acknowledgment, alarm clearing, alarm hiding, and ad hoc alarm suppression.
- Custom context menu items can be scripted allowing customized control behavior.
- In the CygNet TWC web view a context menu is available with access to CygNet point and alarm data, including current value details, alarm acknowledgment, alarm summary, and trending point data on a quick chart. The TWC context menu also supports adding any CygNet point presented in the main web view to an ad hoc chart.
This control is supported in the Canvas Native view and the CygNet TWC web view.
The Canvas Alarm Grid mirrors many of the features available in the CygNet CAS View Control.
Alarm Grid Example
The following image shows an Alarm Grid.
|
Alarm Grid, showing Toolbar Filters and Context Menu on point in alarm |
Property Inheritance
Property Inheritance
Property inheritance, or sending and receiving, is a widely used concept in Canvas. The application supports an explicit relationship between screens, objects, and controls, where certain property values, such as facilities and SiteService details, are passed from one element to another via an inheritance framework. Screens, objects, and controls can be configured as property senders or property receivers and provide configuration options where you can explicitly define the source of the facility and SiteService. Depending on how you have your screens, objects, and controls configured, the facility and SiteService may be received from any one of the following sources:
- from itself — indicated by selecting <Self> and then explicitly configuring the property
- received from the screen — indicated by selecting Screen, which is always present as a sender
- received from another control — indicated by selecting the Name of the sending control.
Broadcasting
Screens and objects support an additional notification option to broadcast their facility and SiteService selection changes to other open screens. If configured, a <Broadcast> option is available to source the screen's facility and SiteService properties from another open screen.
For example, a Text Tool can be configured to get its facility from the screen and the screen can be configured to get its facility from a Tag Chooser. Or Screen_A might source its facility from Screen_B, which gets its facility from a Tag Chooser.
Receiver or Sender
The Alarm Grid supports property inheritance as a receiver of its SiteService and facility, and as a sender of its facility:
| Receive | Send | ||
|---|---|---|---|
| SiteService | Facility | SiteService | Facility |
|
self (CAS) screen |
screen other controls |
none | screen other controls |
The Alarm Grid is multi-facility aware and the level of a configured hierarchy selected (from an associated Tag Chooser) will determine on how many rows will be loaded into the associated Alarm Grid.
