AVEVA Product Feedback


Add a new idea Subscribe
Status Tell us more
Categories Asset Framework (AF)
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Better visual distinction between reference types in the element hierarchy in PI System Explorer

Currently, you cannot visually distinguish between a composition relationship and a primary parent-child relationship, or between a secondary parent-child relationship and a weak reference in the element hierarchy in PI System Explorer. Please allow all of the built-in reference types to be visually distinguishable from each other from the element hierarchy. Perhaps the dotted line that connects the parent to the child could be formatted (solid versus dotted?) in addition to modifying the child element's symbol.
  • ADMIN RESPONSE
    Aug 19, 2022
    Can you provide specific use cases? For example, what would you do differently if such distinctions are available visually? Composition and parent-child references primarily affect what happens when objects are deleted. It really doesn't affect visualization. Any details you can provide would be helpful.
  • Attach files
  • Guest
    Reply
    |     Oct 24, 2024

    As Kenneth has said, essentially the problem is that there is no easy way to determine where different reference types have been used unless you interrogate the element in very specific ways, which makes it difficult to use this feature effectively at scale. Suggestions that wouldn't make the UI cumbersome:
    1) It could be a hidden Status Bar option alongside 'Show Unique ID' that could be manually enabled by users.
    2) It could be included as an option in the Element Search dialog, allowing you to find instances of a particular reference type being used

  • Guest
    Reply
    |     Aug 19, 2022
    The strongest use case is to make sure that the correct relationships are used. This can always be checked in bulk with PI Builder as well, but PI Builder is not as visual as PI System Explorer. It's easy for people to just use the default relationship for everything, even if another one would have been more appropriate, so it would be nice to be able to detect and then correct this easily. My suggestion is obviously not critical. It just helps with getting an understanding of the relationships between assets at a glance.