Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Disabling Alarms in a Hierarchy all-at-once #61

Open
slominskir opened this issue Feb 10, 2025 · 0 comments
Open

Allow Disabling Alarms in a Hierarchy all-at-once #61

slominskir opened this issue Feb 10, 2025 · 0 comments
Assignees

Comments

@slominskir
Copy link
Member

slominskir commented Feb 10, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant