In Vision/Perspective, assuming that I've got some property that's based on an expression on some other tags, is there any reason to bind other expressions to that property, rather than pulling the expression out into a tag and binding to a tag (so I e.g. can get history over that)
If you have any reason for the history of that combination, sure.
If you will have multiple Perspective sessions looking at that live value, or Perspective + Vision, definitely. Will save CPU if only done in one place.
If Vision will be the only user of the combination (without history), compute it either in a Vision Client Tag or in the affected Window as a custom property's expression binding. This will save the gateway workload of doing that expression at all.
2 Likes