nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Worksite Properties for checked-out Word Documents

RhysFomAIM

Hi,

I'm looking at a problem with an application WorkSite integration and wondered if anyone could shed any light on an issue i've come across. Apologies if this has been answered\is well know, I havent been able to find any details elsewhere.

When a file has been checked out of WorkSite, and is then local, functions such as WorkSite properties do not function. I get the message

"Unable to display WorkSite document profile information. (Filename) does not exist in any of the databases of the sessions you are logged in"

This is despite being logged into our (one and only) WorkSite server.

It seems like as soon as you check out a document it is completely disconnected from WorkSite, so if you print, email or look at the properties then the link to WorkSite isn't there, and details are not recorded against the document. If this has been a problem for anyone before, is there a way of programmatically making the word document aware of the WorkSite server.

Many Thanks

Find more posts tagged with

Comments

jny

Did you use the Checkout command or the Open command to checkout this document from within the WorkSite Client? If it's the former, what is the checkout path? Is it portable path or user-selected path?

RhysFomAIM

I used the Checkout command, where the path is the users temporary directory.

Would the open command have effectively the same effect as the open through Mailsite?

jny

If you want to mimic the open command that is executed from within FileSite, then you should invoke an instance of the IMANEXTLib.OpenCmd Object as this command object automates the tasks of checking out the document file to the portable directory, and opening the document in its native editor.

If you want to check out the document to a temp directory -- not the WorkSite portable directory -- then you would need to use either the API's of the native editor, namely Word Object Mode when it's a Word doc, or Shell Execute to open the file from its checked out directory. If you do this, then the CheckoutCmd object is the approriate one to invoke.