You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current/existing ALH alarm app allows users to disable alarms in a tree-like hierarchy such that all nodes below a given node are disabled all at the same time.
Currently JAWS defines an attribute for each alarm to link a parent alarm such that a dependency hierarchy is formed. However, the original idea was for this hierarchy to represent alarms that are "Masked" by a parent alarm in order to avoid alarm floods. This is a similar and related idea. We need to figure out if the "Masked By" hierarchy is the same as the "Disabled By" hierarchy. I assume both supporting Disabled By and Masked By behaviors are desired, but clarification needed.
Note: We currently have the fields in the database for Masked_By, however, no values have been configured. The JAWS app currently doesn't do anything with alarm hierarchy.
Note: There was a stated goal early on to avoid a graphical hierarchy in the new app. If I'm remembering correctly it was because many/most alarms don't fit into a hierarchy. So we need to support a hierarchy, but not force it on all alarms.
Note: The workaround at the moment is to take advantage of the multi-select ability on the Notifications tab to select multiple alarms at once and then apply the Disable to them all-at-once.
The current/existing ALH alarm app allows users to disable alarms in a tree-like hierarchy such that all nodes below a given node are disabled all at the same time.
Currently JAWS defines an attribute for each alarm to link a parent alarm such that a dependency hierarchy is formed. However, the original idea was for this hierarchy to represent alarms that are "Masked" by a parent alarm in order to avoid alarm floods. This is a similar and related idea. We need to figure out if the "Masked By" hierarchy is the same as the "Disabled By" hierarchy. I assume both supporting Disabled By and Masked By behaviors are desired, but clarification needed.
Note: We currently have the fields in the database for Masked_By, however, no values have been configured. The JAWS app currently doesn't do anything with alarm hierarchy.
Note: There was a stated goal early on to avoid a graphical hierarchy in the new app. If I'm remembering correctly it was because many/most alarms don't fit into a hierarchy. So we need to support a hierarchy, but not force it on all alarms.
Note: The workaround at the moment is to take advantage of the multi-select ability on the Notifications tab to select multiple alarms at once and then apply the Disable to them all-at-once.
See: #11
The text was updated successfully, but these errors were encountered: