Adding Source and Acknowledgement Users in Events (Detectors) Lists
-
Hello again everyone.
I try to add the source and the name of user that acknowledges the event every time, in event list.
Is this possible? I try to find a way by ma-events-table.
Also, could be possible to change the color of severity-priority flags in alarm level?
Thank you.
-
This post is deleted! -
@nikospps said in Adding Source and Acknowledgement Users in Events (Detectors) Lists:
Hello again everyone.
I try to add the source and the name of user that acknowledges the event every time, in event list.
Is this possible? I try to find a way by ma-events-table.
No this information is not coming back via the REST API currently. It is something we need to do.
Also, could be possible to change the color of severity-priority flags in alarm level?
Thank you.
This you can do via a custom stylesheet. Copy this section into your style sheet and change the colors.
/* Alarm Flags */ .alarm-flag.ALL, .ma-alarm-level-all, md-icon.ma-alarm-level-all, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-all { color: #000000; } .alarm-flag.NONE, .ma-alarm-level-none, md-icon.ma-alarm-level-none, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-none { color: #9E9E9E; } .alarm-flag.INFORMATION, .ma-alarm-level-information, md-icon.ma-alarm-level-information, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-information { color: #00BCD4; } .alarm-flag.IMPORTANT, .ma-alarm-level-important, md-icon.ma-alarm-level-important, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-important { color: #2C919E; } .alarm-flag.WARNING, .ma-alarm-level-warning, md-icon.ma-alarm-level-warning, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-warning { color: #4CA631; } .alarm-flag.URGENT, .ma-alarm-level-urgent, md-icon.ma-alarm-level-urgent, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-urgent { color: #FDD835; } .alarm-flag.CRITICAL, .ma-alarm-level-critical, md-icon.ma-alarm-level-critical, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-critical { color: #FF9800; } .alarm-flag.LIFE_SAFETY, .ma-alarm-level-life-safety, md-icon.ma-alarm-level-life-safety, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-life-safety { color: #F44336; } .alarm-flag.DO_NOT_LOG, .ma-alarm-level-do-not-log, md-icon.ma-alarm-level-do-not-log, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-do-not-log { color: #9E9E9E; } .alarm-flag.IGNORE, .ma-alarm-level-ignore, md-icon.ma-alarm-level-ignore, md-input-container:not(.md-input-invalid).md-input-focused md-icon.ma-alarm-level-ignore { color: #9E9E9E; }
-
It would be really useful if a user could assign an event to another user, like other SCADA systems. For instance, user Tim is not a specialist in the water system, so when he was on watch, he reassigned a water-related event to John. John then tags the event according to its resolution, e.g: acknowledged, pending, or resolved, or reassigned. John then reassigns it to Dexter. Dexter is not a Mango user, but John can write in his name in the reassigned field so we all know who John reassigned it to.
On a related topic, it would be good to be able to prevent purging of events that have comments.
-
+1 on Pedro’s suggestion, but making this available api opens up the possibilities of making this info available to ticketing systems, CMMS, and others. The ability to trigger an event when adding a note or acknowledgement could really be valuable.
-
Thanks for the replies! I believe that is very useful for the development of app all this process!
To the point..i have an event as in the picture:
![alt text]( image url)
in (the first mango) ui, in events list we can see if the event is acknowledged and also the user that made it.
In new Mango's UI we don't have the ability. In many procedures and not only would be useful to know the user that make the acknowledge, as it is also duty issue.
Thanks again everyone.
-
@Nikospps It is indeed something that should be displayed on the new UI. We are working on it - https://github.com/infiniteautomation/ma-core-public/issues/1140