So is the binding backward? Each tag alarm can be configured for an alarm notification pipeline. Wouldn’t that make the alarm notification pipeline a tag alarm property like OpcItemPath?
I have a simple view that I want to embed like a widget. The components are indirectly bound to 3 view parameters. There is a fourth parameter (Path) that points to the folder that contains the values used for indirect binding of the other 3.
Let’s say I wanted to disable the alarm instead of disabling the notification. I would add a parameter called AlarmEnable and indirectly bind it to the alarm’s AlarmEvalEnabled property. A toggle bound to this parameter could be used to disable the alarm.
My binding direction is from component to tags or tag properties. I’m not clear how to bind the tag alarm pipeline back to a view parameter and keep the view dynamic like a widget.
If there is a simpler way to disable the alarm notification in a dynamic view, I would appreciate the process.