AdminRyan McErlean
(Product Manager, OSIsoft)
My feedback
-
4 votes
-
18 votes
We are currently researching this item and evaluating it for a future release.
Thank you for your comment Helmy. To clarify, would you expect all data sets that are in use on a display to be migrated, or that all data sets associated with a display get migrated, regardless of whether or not they are in use?
-
1 vote
The ad hoc workspace can be converted to a new display using the 'Convert to Display' button in the upper right corner. Is this what you mean by saving ad hoc as a new display? If not, please share some additional information to help us understand your request.
-
46 votes
For situation 1, the browser is logging the user in based on who they are logged into the machine as, this is something the is configurable in the browser. This can be adjusted so that the user gets prompted to enter their username and password which would allow them to log on as a user that is different from the user logged into the machine. Otherwise, on a Windows machine you can hold Shift and right-click on the application in the toolbar to get presented with an option to run the browser application as a different user.
For situation 2, there is no way to time out the session with Windows or Basic authentication. You can switch to a different user by closing the browser and using one of the two options mentioned above. The only way to time out the session currently would be to configure PI Vision for claims authentication, which does support session time out.
-
82 votes
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?
-
189 votes
At this time, this item is not currently scheduled for a release of PI Vision. If this changes, this item will be updated to reflect the current status.
The font size used in trends is not currently configurable. This page is for the request to support font size configuration for trend, table, and gauge symbols.
-
244 votes24 comments · PI Vision » Display Management / Displays Page · Flag idea as inappropriate… · Admin →
We are currently researching this item and evaluating it for a future release.
Work on this feature has not been started, so it will not be included in PI Vision 2019. If this item gets planned for a release or if development work on this item starts, we'll update the status of this item to reflect that. If you'd like to see all requests that will be included in PI Vision 2019, you can filter by the status of 'Started / In Development', all items that are being worked on for the 2019 release will mention PI Vision 2019 in the status notes.
Richard,
If the sites are identical and have the same AF structure you should be able to swap the site name natively in PI Vision by swapping to root asset for the display. This would allow you to either reuse the same display(s) for all sites, or swap the root asset and then save as to create distinct displays for each site without having to manually remap the symbols. You can swap the root asset in a few different ways, for example with the asset dropdown list, with navigation links, URL parameters, etc. Documentation for using the asset list in this way can be found here: https://livelibrary.osisoft.com/LiveLibrary/content/en/vision-v2/GUID-DC4D3A7B-94C9-43C1-9AA2-1846D7F66391
If you'd like any additional information on this topic please let me know.
-
14 votes
This behavior has not been changed in the PI Vision 2019 release. The PI Vision Display Utility does currently support overwriting when copying displays between servers, however, in order to overwrite it requires that the display name and display ID be identical on both servers. This is only possible if the production system SQL database was created from a backup of the test system SQL database (or vice versa).
We understand that this is a significant limitation and will be considering ways to address this. This item will be updated if there is a change in status.
-
9 votes
To accommodate colorblind users, allow multistates to control not only color, but also the shape displayed, and the line thickness of the shape.
-
2 votes
Column widths can be adjusted by clicking and dragging the column dividers in the table. Please give this a try and let me know if you have any issues.
-
7 votes
If you have a chance, we’d like to learn more about the use case behind this request.
By default, PI Vision will automatically pick up and use the time zone of the client machine a user is running their browser on, so all times should be displayed in a user’s local time zone.
If this isn’t the behavior you are seeing, or if you have a use case where users need more control over the time zone being used to display data please let us know.
Thanks for this feedback Kevin, we have a separate item to track this request. I've gone ahead and added you as a supporter of that item: https://feedback.osisoft.com/forums/320517-pi-vision/suggestions/33897457-date-picker-pop-up-calendar-for-time-manipulation
-
55 votes
At this time, this item is not currently scheduled for a release of PI Vision. If this changes, this item will be updated to reflect the current status.
AdminRyan McErlean
(Product Manager, OSIsoft)
supported this idea
·
-
9 votesAdminRyan McErlean
(Product Manager, OSIsoft)
supported this idea
·
-
114 votesRESEARCHING / EVALUATING · 2 comments · PI Server » Analytics & Calculations · Flag idea as inappropriate… · Admin →AdminRyan McErlean
(Product Manager, OSIsoft)
supported this idea
·
-
90 votesAdminRyan McErlean
(Product Manager, OSIsoft)
supported this idea
·
-
4 votesAdminRyan McErlean
(Product Manager, OSIsoft)
supported this idea
·
-
5 votesAdminRyan McErlean
(Product Manager, OSIsoft)
supported this idea
·
-
34 votesAdminRyan McErlean
(Product Manager, OSIsoft)
supported this idea
·
-
33 votesAdminRyan McErlean
(Product Manager, OSIsoft)
supported this idea
·
-
4 votesAdminRyan McErlean
(Product Manager, OSIsoft)
supported this idea
·
Currently the migration utility will attempt to access PI Vision as the user who is currently logged into the machine. How would a login prompt be useful in this case? Does the user need to enter login credentials so that they can authenticate as a different user (a user other than the user currently logged into the machine)?