You are viewing limited content. For full access, please sign in.

Question

Question

Web Access URL for a file in LF

asked on October 31, 2016 Show version history

Hi,

Our client is using LF 10.1 RIO and are trying to generate a web URL to hyperlink to a document. I can think of generating URL in 2 ways A) Web Access, but this is not ideal in most cases as users generally prefer using desktop app and B) by using a WF but it feels like a workaround. The client wants to right click a file which they search and locate in windows desktop app and then copy it's URL in order to hyperlink into their documents in progress for references.

In this org, LF service and Web Access are installed on 2 separate servers.

Is there a way to generate a web URL for a file from LF desktop app (for ex. by right click menu)?

Is there another way to hyperlink a file if not this way?

Thanks,

Adarsh

0 0

Answer

SELECTED ANSWER
replied on November 3, 2016 Show version history

The simpest way is to make a toolbar button with the command 

C:\Program Files (x86)\Internet Explorer\iexplore.exe http://lfwaserver/laserfiche/DocView.aspx?db=%(RepositoryName)&docid=%(SelectedEntries)

like this:

where lfwaserver is the Web Access server. This will launch IE directly to the document viewer for the selected entry.  More information about custom toolbar buttons can be found in the online help. To improve it a bit, you could write a helper application that is called instead of iexplorer.exe, to better deal with the case when the user runs the command with an invalid selection (multiple documents, folders, etc). For more information and sample code, check out the second half of this presentation and the CustomButtonManager project in ClientAutomation Samples.zip in the SDK sample code.

1 0

Replies

replied on November 1, 2016

This is not possible out of the box. Workflow is probably the easiest way if you have it configured already. Another way to do it is with a custom toolbar button on the desktop client, but that requires some integration work. If you are interested I could whip up some sample code.

2 0
replied on November 2, 2016

Hi Robert,

If you already have something, please can you share?

Thanks,

Adarsh

0 0
SELECTED ANSWER
replied on November 3, 2016 Show version history

The simpest way is to make a toolbar button with the command 

C:\Program Files (x86)\Internet Explorer\iexplore.exe http://lfwaserver/laserfiche/DocView.aspx?db=%(RepositoryName)&docid=%(SelectedEntries)

like this:

where lfwaserver is the Web Access server. This will launch IE directly to the document viewer for the selected entry.  More information about custom toolbar buttons can be found in the online help. To improve it a bit, you could write a helper application that is called instead of iexplorer.exe, to better deal with the case when the user runs the command with an invalid selection (multiple documents, folders, etc). For more information and sample code, check out the second half of this presentation and the CustomButtonManager project in ClientAutomation Samples.zip in the SDK sample code.

1 0
replied on November 3, 2016

Thank you Robert.

I will have a bit of play with this and see how we go :)

Regards,

Adarsh

0 0
replied on November 6, 2016

Hi Robert,

I recently configured as you suggested. It certainly looks like the easiest option to have in order to obtain a web page.

Can we push this to all users using Attributes? If yes, do you know what Attribute we can use?

I can not thank you enough already :)

Adarsh

0 0
replied on November 7, 2016

Toolbar buttons are not controlled via attributes, they are stored locally in the registry. Your options are to configure them manually on each machine or use the SDK (specifically CAT, see my earlier post for more information). You could also push out the registry changes via group policy, but the problem there is that a user's previous toolbar changes would be wiped out.

0 0
replied on October 31, 2016

Adarsh,

 

What about a button in the Client menu bar that runs the Workflow? It could then email them the hyperlink?

1 0
replied on November 1, 2016

You could also try a "URL" field on your documents. Depending on your users' flow and what percentage of documents needs this field, you could approach this several ways:

  1. Allow users to add this field manually and have a default value that uses the entry ID as a token to generate a URL (https://yourWebAccessServer/laserfiche/DocView.aspx?db=yourRepository&docid=%(Id) )
  2. Add that fields (with the same default value) to templates for documents you know it will be needed for
  3. Have Workflow append this field to documents (might be overkill to process all documents this way)
1 0
replied on November 2, 2016

Thank you for your detailed answers. I would have loved to see an out-of-box option to copy hyper-link. But I am happy to produce some alternatives.

I will suggest using a workflow to generate URL on demand to update a text metadata field with the URL. That way they can get the link with least number of mouse clicks.

Thanks,

Adarsh

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.