True, but I think the use case is mostly around having a link to a document/form in either webaccess/weblink form, but needing it in another. 

Example: I have a weblink URL that's accessible to all staff via an intranet site or email sent to all staff. If I need to edit it, I have to click on that link, find out where the document is, open webaccess, drill down to the document, and then finally edit it. This is a lot more time consuming than clicking the link and then a button to get edit access.

Another scenario would be if I'm editing a document and need to send the weblink URL to someone who doesn't have edit permissions. I would have to edit/save the document, open weblink, refind the document, and then copy the URL.

Hi Robyn,

Thanks for the use-case, it helps understand what's going on.

I believe you may be able to set this up from the web client through a custom toolbar button. Assuming your weblink server is at a fixed known location (which I assume it is), you should be able to create a button that simply redirects you to the WebLink server and auto-populates the currently selected or open document ID via token. 

I don't believe there is a similar way to do that the other direction at the moment though.

Update to this thread, we are facing this issue right now.  For a long time, we have had a certain group of users that would search for documents through Weblink, then use a custom toolbar button to open the document in the editor if needed.  It is my understanding that Weblink 11 will not allow this functionality, and we are having to take a much more roundabout approach to accommodate their process. 
 

For example, in the web client, one cannot open a search page, even with a properly configured url, if they get prompted to log in.  They have to log in, then click advanced, then go to save searches, then select the one they need, and THEN they can perform the search they used to access via a single click.  Furthermore, linked documents are a bit harder to find in the web client vs weblink, and we have to retrain them on that.

I agree it would be nice to be able to switch between environments, or at least improve tools and flexibility in web access.

Have you been given a reason why WebLink 11 wouldn't allow for this? I don't see a reason why it wouldn't work. You would probably need to rebuild the custom toolbar button as I don't think it will migrate from version 10 to 11, but it should still be possible.

I'm picking this up from an employee that left a few years ago.  He had a custom toolbar button in Weblink that took the document id for the currently-open Weblink document and opened it in Web Access.  I do not know how he did that, and have been unable to find documentation on the subject.

My statement that it isn't possible in weblink 11 is based on what one of our vendor's developers told me; that such customizations are getting more restricted, and a custom button like that can't be done in WL 11.  If you have any ideas, instructions, or link references, I would be happy to receive them!