PI Vision Displays Management Process
We have noticed as PI Vision gets adopted, organization of displays and content is becoming more and more cumbersome.
It has become obvious that PI Vision is easy enough for any average person to design good quality displays that could be considered as part of the company's knowledge retention strategy.
Therefore, similar to the concept of crowed sourcing, our vision is to "crowed design" in which James Dryden described it best in a reply Group Ownership Of A Display - PI Vision 2017 .
I can envision a system in which users save personal copies of "published" shared displays and make changes they would like to see in the shared display. Then when ready, they could submit their new display for approval, and once approved the contents of the shared display could be removed and replaced with the contents of the submitted display. This could be made even more effective with the use of folders that were added in PI Vision 2017 R2, since you could have an "official" folder to which only Administrators have rights to add displays.
What James Dryden described is the exact process we are trying to execute, but its manual and weakly coupled.
It would be great if PI Vision Publishers had a button in the displays they own called "Proceed to Publish" to submit the display to the administrators for publishing.
This would be great! We are also wanting the ability for an Active Directory group to be the Owners of a Vision screen, not an individual.