Currently PI Vision 2024 includes the ability to 'set database search root' for users in the PIVision/Admin portal. Using this feature can significantly improve user experience and adoption of PI Vision - every click you can remove for an operator/user, the better your chances of them being satisfied using the software. (Note - I found with the addition of PI Connectors creating AF hierarchy trees, the AF structures include many 'parent' levels that users must click through until they see a recognizable asset which adds friction to the process)
However, implementing this search root setting feature (to hide the unnecessary levels and remove model navigation 'clicks') currently suffers from 2 main flaws:
Users have no self-serve option. This requires admin access to configure.
Search roots can only be set BY NAMED USER.
As a result, while the feature is great, it is very difficult to manage and becomes tedious or cumbersome for admins.
I see a few mentions of this in other feedback posts (see PIVISION-I-1166 & PIVISION-I-1828), but have not been acted on. I'd like to renew support for similar ideas. However, my request is that the 2 challenges I list above be addressed in SOME way. Below are a few options and I'd request as many as possible be implemented, but won't claim to know which is best for most people or which is quickest/easiest to implement. Thank you for your consideration.
Options:
Allow for database search roots to be configured (still by admins) according to PI Identities (or AD groups) instead of individual user. This would significantly reduce the amount of administration required when configuring Vision for a large company with changing users.
Add a 'global' default search root option. All new users would have this search root unless otherwise specified in their specific user settings. This could work where 'most users' at a site would be served with similar setting, reducing the administration to just the exceptions for those needing greater or more restrictive access.
-
Migrate this setting to be configured by each individual user instead of admins.
This could be a default setting in a user profile, or
a session-based selection in the Asset Search/Nav bar where users select 'set current as root'
This option is the most dynamic and nearly eliminates the administrative burden - just point users to the documentation on how to select it for themselves! And if users are building displays for different areas of interest on different days, they can control the setting to improve the ease of build user experience as needed.
Attached picture is just confirming the settings/current location I'm referring to.
