Navigation: Link to a Display with Asset Context
When linking to another display via text hyperlink or a button, be able to pass in the current asset/element context of the display you're looking at into the destination display.
For example, if looking at a Wind Turbine Overview display for Wind Turbine 3, if I click on the link for the Gear box detailed display, then the Gear box display will show the gear box information for Wind Turbine 3.
The PI Vision development team has completed work on Drill-in Navigation in PI Vision 2017 that enables linking to another PI Vision display from any symbol on a display with options to pass the asset context of the selected symbol and the time range of the display. Upgrade to PI Vision 2017 to take advantage of this and other key new features. You can read about the key new features in PI Vision 2017 in our release announcement here: https://techsupport.osisoft.com/Troubleshooting/Releases/RL01216
Wesley Smith (INACTIVE - DO NOT USE) commented
We are currently integrating thousands of power strips on thousands of server racks. We are using Coresight to be our primary display for users but navigation is causing a nightmare.
Example: We have a page for each room that is custom to the room layout that displays hyperlinks to pages for the racks. these are intended to be 1 template page per rack configuration that displays rack information. These pages need to have links to the power strip pages that need to be templates related to the strip type.
Now we can set it up just fine for this to work to the rack by setting the hyperlinks in the room to reference the AF element for the rack. However, there is currently no way for me to use the same approach to get to the power strip. This leaves us with the only option of leaving a static hyperlink to the power strip template page and then have the user select the power strip they want from the drop-down asset selection. Meaning that they will have to look through hundreds if not thousands of strips to find the one they need.
If this suggested fix were implemented, it would allow us to pass the rack info to the strip page easily.
For anyone curious for another approach to this please check out this suggested solution as well. It would also make this doable.
"Help me OSISoft, you're my only hope!"
Expanding on this idea, it would be a powerful feature to allow custom symbols to transition to other displays (using the transitionTo method of the $state provider) and be able to pass a configuration object into the state variables. Currently it does not appear that the $stateProvider is set up to allow this.