We want to use security on tags and split the tags up in groups of control.
We also need to visualise that an operator can or can’t control something. But I seem to be lacking a way to link the tag configuration to the visualisation.
F.e. an operator who’s only responsible for the packing area can only control motors of that area.
When he clicks on a motor, he sees a popup that shows a motor instance. But the controls should be enabled or disabled based on the role of the operator.
The popup is the same, so I need to get the info from the UDT instance in some way.
I thought about getting it from the tag security directly (via some expression or runScript). But I can’t seem to find it that way.
My second thought was to add an UDT parameter, and base the tag permission on that. Then we could read the parameter (via some bound memory tag) to visualise it. It would be less flexible, but at least we wouldn’t have to define everything twice.
Alas, that doesn’t seem to work either. It doesn’t seem to accept curly braces as parameter replacements.
Is there a way to get a link between vision and the tag permissions? Or are we just doomed to define everything twice and get into inconsistencies?
Does anyone actually use role-based permissions on tags?