When making alarm changes, sometime you will notice the change does not go through to runtime if you currently have [Alarm]UseConfigLimits=0
This is because the alarm server reads from the database instead of the rdb files, failing to recognize that alarms configuration has changed.
This can be rectified by applying the ini parameter [Alarm]UseConfigLimits=1, forcing the alarm server to read from the rdb file instead. However, this is occasionally impractical if the alarm database's data is necessary.
Guest
|
Idea business value
This would streamline how we work with alarms, making it much easier to make changes to alarms and alarms category without having to rely on the paramater [Alarm]UseConfigLimits |
|
| Idea priority | 3 – Some use to my company |
