Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

128 VOTE
Status Completed
Categories Symbols
Created by Guest
Created on Aug 18, 2022

Multistate: Change text color

In multistate, we are able to change background color. We would like to be able to change text (letters, words) colors for text and value symbols with multistate.
  • ADMIN RESPONSE
    Aug 18, 2022
    In PI Vision 2020, new multi-state capabilities were introduced including the ability to change text color on the value and text symbols. For additional information on PI Vision 2020, please see the release announcement here: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000031641
  • Attach files
  • Guest
    Reply
    |
    Aug 18, 2022
    This would be super helpful. Only being able to change the background limits our use.
  • Guest
    Reply
    |
    Aug 18, 2022
    Some customers prefer black or darker backgrounds for display for readability. Lighter backgrounds have been shown to contribute to eyestrain. The colors red, yellow and green are standards in MMI applications (SCADA) in terms of representing a state for an operator to see. With the current multi-state feature, it is then impossible to present the actual value in a readable form and use those colors with a dark background. I know the asset comparison table now features multistate - but the desire is for it to work like ProcessBook - a table is not always a good option. It would be helpful to hear some feedback from the team - is it possible, is this discussion in another thread...
  • Guest
    Reply
    |
    Aug 18, 2022
    multistate
  • Guest
    Reply
    |
    Aug 18, 2022
    Agree, and to clarify, this is for value symbol multi-state as well, not only for static text.
  • Guest
    Reply
    |
    Aug 18, 2022
    Any update on this?? 
  • Guest
    Reply
    |
    Aug 18, 2022
    this feature would add considerably to pi vision displays
  • Guest
    Reply
    |
    Aug 18, 2022
    Any update when will this be considered and implemented please?
  • Ryan McErlean
    Reply
    |
    Aug 18, 2022
    This feature is not currently planned for a release of PI Vision. If this changes, the status of this item will be updated and if you are subscribed for updates then you will receive a notification email. In order to help us understand the importance of this request and prioritize it appropriately relative to other requests, it would help if you are able to share the impact this feature would have for you. Is this a high priority for you? Please help us by letting us know how having this feature (or how not having this feature) affects your use of PI Vision. Is this impacting the adoption and use of PI Vision? If you are using PI ProcessBook, is this something that would affect or potentially prevent users from migrating to PI Vision if this feature is not implemented?
  • Guest
    Reply
    |
    Aug 18, 2022
    In response to Ryan McErlean, "This feature is not currently planned fo..." In our case, it is preventing our ability to build better displays including the use of PI Vision features such as Collections and Filtering. So a number of legacy ProcessBook displays running in PI Vision are still required to meet visualization needs and these displays are more complex to build/maintain.   In terms of priority - I would classify it as high.  Asset comparison tables are limited in display options, so collections are the better choice.  But we cannot easily alert to multiple conditions on the same collection object because of the current fill behavior for multistates.  
  • Pete Long
    Reply
    |
    Aug 18, 2022
    one more reason ProcessBook is still the visualization of choice with our company
  • Guest
    Reply
    |
    Aug 18, 2022
    For migrations from ProcessBook, this affects all value and text symbols, which makes the migration not work as well. In many cases, a multistate value symbol may have a default text color that doesn't work well after migration. For example, the text color is Green, and the multistate colors are Green and Red. Now after migration, the value will either be Green on Red (difficult to read) or Green on Green (impossible to read).
  • karthi44
    Reply
    |
    Aug 18, 2022
    My scenario explained below: Element A - Has 10 Attributes Element B - Has 8 Attributes Element C - Has 10 Attributes All from a same template - where Element B has 2 excluded attribute. Now, In PI Vision - If i add all the 10 Attribute from Element A and convert to collection... I will see N/A for the missing/ excluded attribute in Element B ... ( This is annoying as we cannot hide it easily.) So IF we have the ability - Hide excluded in pi vision or hidden option for the excluded attribute it will be awesome. And, If we have Multi-State on the Font color of "Value" It will be easy to hide the N/A values.... This fixes my above issue... Please update the status of this ?/
  • +28