Question

Editing Office Files from a Web App through Web Access URLs

Web Client Version 9 Integrations

Updated March 4, 2015

asked on March 2, 2015

Hello,

We have an asp.net web app that integrates with Laserfiche and we’d like to enable the users to edit Word documents from the app in the same way as in Web Access 9.2 (the document directly opens in Word and the repository is seamlessly updated after saving).

We have tried using Web Access by invoking a URL like the following, expecting that it’ll be the same as opening the file in Web Access:

http://servername/laserfiche/ElectronicFile.aspx?db=Repository&id=6104&mode=officeplugin-checkout

This, however, does not work (in all browsers). When checking the console, there's the following javascript error:

“pluginResults is not defined” in the file “ElectronicFileOfficePlugin.js”

...indow.GetOfficePluginVersion=function(){return pluginResults.officePlugin.versio...

The plugin works fine when double-clicking the file from within Web Access.

We’ve also tried:

lfwa80://officeplugin/http://servername/App_Services/OfficeIntegrationService.asmx?r=Repository&d=6104&t=word

(based on this DevNote: https://support.laserfiche.com/ow.aspx?Laserfiche9.0%2FOfficePlugin%2FWebAccessIntegration)

This opens Word, but after authenticating the Office Plugin complains about an incorrect service URL.

Is it possible to achieve this through a Web Access integration of this kind?

Your help is highly appreciated.

0 0

Answer

SELECTED ANSWER

replied on March 3, 2015 • Show version history

Hey there,

For the office plugin protocol handler URL (lfwa80://...), it's missing the '/laserfiche/' after the server name. It should be:

lfwa80://officeplugin/http://servername/laserfiche/App_Services/OfficeIntegrationService.asmx?r=Repository&d=6104&t=word

If you enter in that URL into your browser, it should launch the office plugin correctly (you'll still have to authenticate, however). Also note that Chrome is very stubborn about considering this URL a search, but it should work in chrome as an embedded link.

Note that the missing '/laserfiche' is a documentation error in the dev note you posted. I'll make sure it's updated.

As for the URL for electronicfile.aspx, I see the same behavior you describe. This appears to be a bug in Web Access 9.2. I've filed a bug report and will update this thread when the issue is resolved. The bug is SCR124831 for your reference. In the meantime, the lfwa80 URLS can act as your workaround.

2 0

Replies

replied on March 3, 2015

Thank you so much.

It works after adding "/laserfiche".

Is there any way to bypass the authentication dialog, perhaps by passing some authentication token? Can the parameter k be used for that?

0 0

replied on March 4, 2015

No.

The 'k' parameter is used for cloning the session in Web Access. It's not useful in this scenario because you're not opening the document through Web Access- you're going straight to the office plugin.

0 0

replied on March 4, 2015

Thanks, Ryan.

That was helpful.

0 0

You are not allowed to follow up in this post.

Question

Question

Editing Office Files from a Web App through Web Access URLs

Answer

Replies

Sign in to reply to this post.