14.12.2020, 23:46
(This post was last modified: 14.12.2020, 23:49 by Erwin van der Zwart.)
No, that is not possible (at least not in a clean way), the alert manager is listening by websocket (and uses polling als fallback) to new alerts in the controller and keeps a timestamp on the client side to store the latest ack alarm, if an detected alarm is newer than the stored timestamp it's marked as unack, so the controller is not aware of this.. (well it kinda is as the client json data is stored in the storage)
But you can use the jump to alert page function that is build-in and enabled by default. Create a plan for the alert manager, add a frame on it with the URL: /apps/data/alerts/ and make sure to enable the checkbox 'Persistent' (Do not unload when hidden) in the frame settings to keep the page listening when send to the background. Also make sure to put a link on this page so you can jump back to your page you came from.
This way you don't need a bell icon as the alert manager is shown instantly when an alarm occurs.
But you can use the jump to alert page function that is build-in and enabled by default. Create a plan for the alert manager, add a frame on it with the URL: /apps/data/alerts/ and make sure to enable the checkbox 'Persistent' (Do not unload when hidden) in the frame settings to keep the page listening when send to the background. Also make sure to put a link on this page so you can jump back to your page you came from.
This way you don't need a bell icon as the alert manager is shown instantly when an alarm occurs.