View document in native format via url - reopened thread...

Morning,

I understand that I can use viewdoc.aspx and pass through &command=ok&ishtml=1 as a parameter to view a document in html format via a WorkSite Web url - how can I force it to open in native format?

In the past, pre-8.0, I've been able to use viewdoc.asp and &command=ok&PortableCheckout=N but this doesn't do anything in Web 8.2.

Are there any other parameters available to do this?

Thanks,
Allan

Find more posts tagged with

Comments

reesbevan

I've managed to use the FileTransferDownload.aspx and pass through the nrtid of the file, and it does open a file in native format but it's a bit clunky - leaves a window open, etc.

Any better way to do this would be great!

Thanks,
Allan

dabird

In WSW when viewing a document in native format, we rely on an ActiveX control or an applet (depending upon the setting in Global Options) to open the file on the client machine. There is no way to open the document on the client machine from the server side for security reasons. In 8.2 we introduced a control to allow environments to not use an ActiveX or applet for file transers. This is what FileControlDownload.aspx does for you.

If you're working within the context of WSW you can use JavaScript to invoke the ActiveX control. If you're working outside WSW, then the only way to open the file in native format is through FileControlDownload.aspx.

1. This example assumes that (1) your custom page is under /worksite; (2) the user has already been authenticated; (3) the client browser can use ActiveX . If these conditions are not met, then this will not work.

To invoke the ActiveX control using JavaScript, call downloadEx, which is defined in <wsw_install>/includes/common.js. The first parameter is the moniker, the second parameter is "view" (for native file viewing). Below is a sample that should work when under your /worksite URL. Just replace 'moniker' with the actual document moniker in the anchor tag.

<html>
<head>
<script language="javascript" src="/worksite/includes/YUI.js"></script>
<script language="javascript" src="/worksite/includes/Utility.js"></script>
<script language="javascript" src="/worksite/includes/Common.js"></script>
</head>
<body>
<script>
//initialize the page.transferControl variable so that downloadEx 
//will invoke the ActiveX control
page.transferControl = TransferControl.ActiveX;
</script>
<a href="javascript&colon;downloadEx('moniker', 'view')">Click here</a>
</body>
</html>

2. The other option, as you've discovered, is to use FileControlDownload.aspx directly in code. The downside to this is that the browser will prompt the user to save or open the document. If you call this URL directly from your code, then you should use this URL in the current window instead of opening a new window.