Our client uses two different PI Vision servers - a 'protected' internal server that is used within their network, which allows for manual entry, and another Read-Only instance which can be used from outside the network. Both access the same AF server.

Our problem is that the URI builder can't handle the complexity of this system layout, and so users of both servers will be pushed by links to whichever server (in this case, internal) has been specified in AF.

The current URI builder functionality is limited because it requires the designer to specify which Vision server it should link to, and so needs you to write the address into the AF attribute, and then to update it when publishing to another server.

Proposal:
Introduce a set of rules for determining the 'implicit' Vision server if none is specified in the URI Builder:
1) If the URI link is called from PI Vision and no server is specified, direct to the same server the request has been received from
2) If the URI link is called from another source (System Explorer, Email, external link) then direct to the default PI Vision server assigned at the Database level (similar to how each database can have a PI Server assigned)