Worksite Web "Integrated Checkout"

Hi,

I'm currently involved in a project using Worksite Web 8.2 and require to untilise the functionality which performs the "Integrated Checkout" on documents. Basically i require to download a document from my app to the client, store this to Worksite via DocProfile.aspx url call and then reopen the document from Worksite from within the "worksiteDialogCallBack()" callback function.

I read that this can be accomplished by calling downloadEXPortable() in common.js, by passing the document moniker. However upon calling this function from my app i receive an js error ->

'null' is null or not an object. It seems that the Applet it requires is not valid

Are there any restrictions or prerequisits i need to be aware of in order to use this method?

Any help much appreciated

Thanks,
RW

Find more posts tagged with

Comments

Migrateduser

Hi Roose, I'm not an expert on this, however I would like to aske you, are you developing your own aspx page for making this work?

If case, remember you have to comment the native aspx in webconfig, and copy yours in scripts folder of worksite web installation.

Not sure if is your problem, hope it helps
Javi

dabird

Rooose,

There are several things you need to set up:

First, "Integrated Checkout" is handled in the ActiveX upload/download control only. The applet will not work.

Second, if you are trying to call downloadExPortable from your custom ASPX page that you've dropped in your worksite installation, you need to (1) write out the file transfer control in your page -- this initializes the ActiveX control; (2) write out clientToAsp -- this is our AJAX control that fetches document properties to verify that the user can perform the operation; (3) initialize some JavaScript variables upon which this implementation relies; (4) if you are also relying on other WSW functionality, you should also configure WSW to use ActiveX for upload/download. This setting is in Global Options.

I have attached a sample HTML page with everything set up. The only thing you may have to modify is defaultDownloadCallback in download.js. In this function, when we call closeDialogWindow(), we don't pass an object. When no object is passed to this function, we expect to be working within the client-side page ui. This sample is not using the page ui, so you will get a JavaScript error. You can modify the call to closeDialogWindow to pass an object literal with a URL:

[Inside <worksite_install>/includes/download.js]
function defaultDownloadCallback()
{
    //code here that opens the document on the client machine

   closeDialogWindow({url:'http://www.google.com'})
}