-
Type:
Task
-
Status: Done (View Workflow)
-
Priority:
Normal
-
Resolution: Done
-
Component/s: None
-
Labels:None
-
Sprint:2017-10A
For alarm handling, we use a single config file which list :
- tablename
- colname
- lower and upper boundaries
Then, we activate/desactivate the alarms according to the current operational mode.
That's not very convenient and easy to improve.
I just have to keep the same logic, but we need to create one config file per mode.
It's only a temporary solution until we have a actual alarm handling as it has been discussed.