Workaround for Failing Nomad Links

[piotrzarzycki21]

@MarkProminic reported that url is not opening in some cases. I will gather more details soon.

UPDATE from Joel; When testing on customer Nomad servers (which are additional servers rather than standalone) we have been seeeing an issue like this:

1. In SHI, click a Nomad link to the local Nomad server
2. Nomad opens. Go through the login process
3. Nomad reports that the database could not be opened. Checking the error message, it shows that Nomad attempted to open the database on a different server.
4. From Nomad, try to open the original server
5. The database list populates, but on further inspection, we see that it is the database list for the second server.

We consider this to be a Nomad issue, and @MarkProminic has reported it to HCL. So far we haven't gotten a response.

This week we stumbled upon a possible workaround. Rather than using the server in the common (nomad-1.acme.com) or abbreviated (nomad-1.acme.com/ACME), we use the canonical format (CN=nomad-1.acme.com/O=ACME). This loads the correct server list when opening the appolication from Nomad.

I confirmed a link in this format works with the Notes client. Note that the / in the canonical name needs to be encoded:

notes://CN=nomad-1.acme.com%2FO=ACME/MyDatabase.nsf/MyView?OpenView

I think this Nomad link should work as well (but I am having trouble getting any links to work at the moment):

https://nomad-1.acme.com/nomad/#/notes://CN=nomad-1.acme.com%2FO=ACME/MyDatabase.nsf/MyView?OpenView

This issue was created to experiment with this workaround. This will probably be an agent-side change.