An error occurred while saving the commentbrendanbell commented
Switching assets on mobile is a critical feature for our organization to be able to scale out adoption of the many screens we have build in PI Vision.
Additional feedback received 1/21/20 from Brendan through Mike Monacella:
I get it, OSI no doubt has more folks wanting a seamless ProcessBook migration toolkit than improved Vision navigation, but what’s going to happen to all those users who migrate their fleets of ProcessBook screens and then find navigating through them a challenge on mobile? I’d encourage you to raise this point with the PM. We want off ProcessBook, too (so we only have one visualization platform to support), but if the usability isn’t there, it’s a much harder sell for us to make to our ProcessBook users. We’ll have the same challenges when we retire ProcessNet later this year. Users will end up using Vision on their laptops via Citrix instead of their phones, which is not ideal.
From this item description it looks like the major pain point with existing RDBMS interface is providing configuration information (to the tags and interface). I would like to understand more if the request behind the connector is to solely minimize providing configuration information to the existing interface and tags?