Multistate: Make visible/invisible based on data item value
Change graphics based on a data item value. For example enhance the multistate functionality so that is it possible to make a symbol visible when a tag/attribute value is equal to 1 and invisible when equal to 0 (or another condition).
This functionality is currently in development for the PI Vision 2020 release.
Oscar Lewis commented
or Attrubute an value
Jonathan Bennett commented
Would be great if hide/unhide would be a multi-state option so if a variable returned "0" the image would hide and if it returned "1" the image would show, for example. This would allow me to layer multiple images on top of each other and have them show based upon variable status.
Juan Cuevas commented
be able to use multi-state the same way as process book.
Be able to hide values/text with multi-state.
There should be a way for a visual element to display when based on the value of the data. Like if the downtime for a piece of equipment reaches a certain number, the display should appear; if the downtime is below the threshold-the display disappears. I've kind of done this with the multi-value to be the color of the background when the number is 1 mins or below, and to be red when above 1 mins.
It would be nice to have the option to tie visibility of items (shapes, values, text, trend items) to a bit or multistate.
Hi Paul. Which version are you using? In the 2017 R2 release, the collection's search root should change when the display's asset context changes. In a future release, the visibility property of a symbol can be controlled as part of a more advanced multistating feature. We also want to more appropriately control how we display symbols when their attributes do not exist for the current asset. I'm sorry we were not able to get this done in the initial release.
Paul Booth commented
This is a must.
Tried using the Collection, but some idiot programmed it to display fixed format text when there were no items: whoever decided that really knows how to take a potentially useful thing and mess it up. Sure, allow it to do it if someone wanted it to, but please think about these things. Also I believe that its root search element doesn't change with the screen context: quite an omission that. Perhaps more experienced designers should have been used for a flagship product?.
In a custom symbol we already implemented this behaviour, but it would be beneficial for all symbols.
our specific case: only when an asset is in an exception state, i want to show additional information for that Asset. E.g. show OCAP or SOP information when the asset is out of control