version 8.1
The web page that users are directed to when acknowledging an alarm seems to have some bugs and/or limitations - I'm looking for workarounds if anyone knows of any.
The biggest issue is that the alarm is identified to the user by the [Name] @ [DisplayPath]. The Ignition docs say that the [Label] property is provided as an alternative, user-friendly name for the alarm, and even says that if the Label is left blank, the [Name] value will be used (where???). I would think that the [Label] field would be used on the remote ack web page, but in my testing it appears to be ignored even when its value is different from [Name]. In our case, this results in cryptic descriptors being passed to the user instead of the friendly name.
The next issue is that we leverage a fair amount of Associated Data that gets passed to the user in the notification email. It would be nice to be able to include this data on the remote ack page, to aid the user's awareness of what they are acking.
Lastly, the remote ack page does not appear to reflect any of the custom Perspective branding from the gateway config. It would be nice to be able to replace the graphics and update the style to be consistent with the rest of our UI.
Maybe I could just build my own remote alarm ack page, and use a script block in the alarm pipeline to generate my own email with a link to that page, passing the alarm GUID as a query parameter....hmmmm
