|Alarm group identifier||The unambiguous identifier of an alarm group in the application.|
|Displayed group name||The displayed name of an alarm group. It is used in viewers, print-outs, etc. The name doesn't need to be entered (can be empty string) - then the group name is not displayed anywhere. It has sense only if there is only one alarm group in the application.|
|Area||Marking the area where the alarm group belongs (group or subgroup). All alarm items of one PmaAlarmGroup object belong to the same area. It goes about an arbitrary string that enables to users easier filtering the set values when watching the group. It is useful first of all when more objects PmaAlarmGroup store the data to the common file (see the "Parent enabled" configurator).|
|State viewer||Path (relative) to registered #state viewer represented by PmaPanel with PmgAlarmStateViewer object. If not set then no registered viewer is set for this alarm group.|
|History viewer||Path (relative) to registered #history viewer represented by PmaPanel with PmgAlarmHistoryViewer object. If not set then no registered viewer is set for this alarm group.|
|Remote group (client)||If checked, then the group is not meant for generating alarm items but it serves only for the remote viewing another alarm group. All operations that would have resulted in writing to disk, will fail over such group.|
|Number of inactive, unacknowledged alarms (blue) to keep||If it's not zero, then when activating the inactive, unacknowledged item (blue) the item is activated (red) but at the same time the original inactive, unacknowledged item (blue) is kept so that both items are seen concurrently (red and blue). After the acknowledgement of the inactive, unacknowledged item (blue), this item is automatically removed. The configurator allows to set the maximum number of inactive, unacknowledged items (blue) (copies of the active item) for each alarm item. The zero means that no older occurrence of the inactive, unacknowledged alarm items (blue) doesn't arise, each alarm item occurs only once (no copy).|
|Hide inactive acknowledged (green)||It allows to define whether to display inactive confirmed (green) alarms. Inactive confirmed (green) alarms can be divided into two types. New, non-initialized (non-existing so far) alarms and alarms that have been active in the past, but ceased existence.|
0 = Show all - Inactive confirmed (green) alarms will all be displayed, i.e. the alarms of both types (i.e. both new and expired alarms will be displayed).
1 = Hide all - Inactive confirmed (green) alarms will not be displayed (i.e. no new and no expired alarms will be displayed).
2 = Hide only new non-initialized - Inactive confirmed (green) alarms of the new non-initialized type (not activated so far) will not be displayed. Inactive confirmed (green) alarms that have been active in the past and are ceased now, will be dispayed (i.e. new alarms will not be displayed, ceased alarms will be displayed). See the "PmaAlarmGroup > Group > Change inactive confirmed (green) CEASED to NEW non-initialized alarms in [s] (-1=never)" configurator.
|Delete inactive acknowledged (green) (valid only for dynamically created items)||If checked, then the alarm item is removed from the list if it becomes inactive and acknowledged at the same time (see the state inactive acknowledged (green)). It has sense only for the dynamically created alarm items. The same value can be set even for alarm item templates, see Delete inactive acknowledged (green).|
|Change inactive confirmed (green) CEASED to NEW non-initialized alarms in [s] (-1=never)||The configurator sets/disables the time delay in seconds, before the inactive confirmed (green) CEASED alarms are automatically switched to inactive confirmed (green) NEW non-confirmed alarms. The value -1 disables the automatic switching.|
|Sound notification||The way of sound indication of an alarm items state.|
|Sound parameters||Parameters entered here can be modified by any PmAlarmItem object.|
|Parent enabled||If checked, then the parent group can be set in the "Parent" configurator.|
|Parent||alarm items (PmAlarmItem objects) arise and are stored to disk in the parent group. alarm groups are displayed in the state viewer or in the history viewer also in this parent group. Filtering in the viewer according to the "Area" configurator enables to display items only of the certain alarm group in the frame of the parent group.|
|Allow alarm storage at short application shutdown||If checked, then all active alarms are automatically saved to disk when the application is stopped. #data:GroupId.alb, where GroupId represents the alarm group identifier. When starting the application, if the shutdown time does not exceed the configured time and the application has not been edited, stored active alarms will be automatically re-created with the original information (status, time of origin, acknowledgment time, etc.). The memorized alarms are created immediately after the alarm group is created at startup, before any alarm can occur in the application. Later, when an alarm occurs and it is determined that it has already been created by reading the file, it will be associated with this memorized alarm (no additional will be created). This applies to both scripted and data-extension alarms. This concept allows you to achieve "existence" of active alarms while briefly turning off the application, so neither in states nor in alarm history you will not be able to see that the alarm actually disappeared when the application was stopped and that it was triggered by running the application again. After the application starts, the file will be deleted.|
|Maximum time of application shutdown [s]||Maximum allowed application shutdown time period in seconds (the "age" of the file) after which the stored alarms will be recreated from the file. (-1 = unlimited)|