Can anyone provide insight as to why alarm Notes are not bindable while nearly all other alarm properties are bindable?
We are using a pattern where we create special "Alarm Context" UDT instances for use as external context for our tags that alarm. The various alarm properties bind to member tags of the "Alarm Context" UDT instance. In this manner we can manage the settings for multiple, identically configured alarms in one place. And (optional) expose the alarm settings to be managed in the front-end UI.
Working great except that the Notes property on the alarm configuration is not bindable and we are therefore starting to employ various less-clean work-arounds to meet our needs.
I assume there is rationale for not having the Notes property as bindable, but am struggling to come up with a good reason. The only rationale I could think of (but still don't agree with) is that alarm properties that are dynamic (have bindings) are stored in the alarm_events_data table for each alarm event and perhaps developers thought that perhaps the potentially long-winded alarm notes would create problems. Note that string typed associated data is still possible (with bindings).