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; } } }

Automatically import document from within Word

carlosK

I have a requirement to be able to import an unsaved open document, programmatically, from within Microsoft Word. Based on simple rules, the code automatically configures which workspace folder to store the document in. Currently, to save the document, the code performs the following actions:

• Save the document locally;
• Check-in the local copy;
• Checkout the new document;
• Close the local (non dms) document within word;
• Open the dms checked-out version within word.

This is far from ideal. I’d like to mimic the default optimal save behaviour of worksite, but without displaying any UI, i.e. silently save the document within the dms to a specific folder.

As far as I can tell, worksite is initially saving the unsaved word document within the appropriate folder in nrportable with the new document number and then importing it to the dms from there. I could do this within word, but I cannot get a document number from the dms without checking in a document first. Is there any way to do this?

Regards,

Carlos.

Find more posts tagged with

Comments

jny

I'm unsure at which point in time do you plan on importing this opened local document into WorkSite. But assuming that you're doing it at DocumentBeforeClose, you may get a handle to the dms object (when the instance of Word is connected to WorkSite) using the WorkSite Office Integration Object Model (imano2k.dll/imanoxp.dll). By referencing the type lib to this DLL, you may set up a sink to the iManO2K.IManageExtensibilityObject to call the GetDocumentFromPath method, after you have imported the local file to the WorkSite dms, to get a handle to the imported document object. Then you may add this object to the workspace using the AddDocumentReference(IManDocuments).

The custom footer macro that is distributed with the SDK has code example on how to set up a sink to the iManageExtensibility Object.

carlosK

Thanks for the reply jny.

I've managed to achieve what I set out to do by not using the iManage.dll api directly, rather the iManExt.dll ImportCmd as detailed below.

This code is called from the BeforeDocumentSave event.


ContextItems ctxItems = new ContextItems();
ImportCmd importCommand = new ImportCmd();

ctxItems.Add("ParentWindow", windowHandle.Handle);
ctxItems.Add(CTX_NO_PROFILE_UI, true);
ctxItems.Add(CTX_OPTIMIZED_INTEGRATION_CALL, true);
ctxItems.Add(CTX_IMPORT_DOC_TYPE, docType);
ctxItems.Add(CTX_IMPORT_DOC_DESC, description);
ctxItems.Add(CTX_IMPORT_DOC_AUTHOR, authorId);
ctxItems.Add(CTX_IMPORT_DOC_CLASS, docClass);
ctxItems.Add(CTX_IMPORT_DESTINATION_FOLDER, (NRTFolder) docFolder);
ctxItems.Add(CTX_IMPORT_KEEP_CHECKED_OUT, imCheckinOptions.imDontKeepCheckedOut);