Index
Tutorial Videos
Tutorial videos are available here.
Knowledge Base
Visit our User Forum for discussions & solutions
Configure Standard Folders in XpressDox to save into iManage
This article forms part of the process in configuring the iManage integration. Click here for an overview and full list of the steps to complete the integration.
Configuring Standard Folders in XpressDox to save into iManage
Return to your XpressDox > Settings > Configure.
Take note of the file path at the top, and ensure you are at the top folder level. All settings will apply to this folder and all sub folders, which means that all documents assembled from any folder will be saved into iManage.
Saving of documents:
The Document Save Folder is where you will define the iManage Workspace into which assembled documents should be saved. Typically in iManage that would be something like:
C0001.PL001
- where C0001 is the Client ID in iManage;
- and PL001 is the Matter ID.
To save assembled documents into an iManage workspace, use the drive letter you configured as the Foreign File System in Step 2 of this process:
The way this would be written in XpressDox is as follows:
L:\[<ClientID>]:[<MatterID>]
- where L is the configured drive letter.
The colon and square brackets denote the Client.Matter syntax, and the data elements must be in angle brackets. The data elements ClientID and MatterID are not prescribed; you can decide what you want those data element names to be. However, in order for the integration to work, all three of these components in the path must be present.
So far, that would look like this in the Configuration:
Now add a Pattern for saved file name. Decide how you would like your assembled documents to be named. Remember that this naming convention is highly customizable, can be set at a folder level rather than at the highest level as shown here, or can even be set in the template using the «SetSavedDocumentFileName()» command.
In this example the data element «DocumentSaveTitle» has been used. This is a data element that should be built up in each template, perhaps using an included code template. For example:
«CaptureDataElement(DocumentSaveTitle)»
«OnExitSet(FullName,DocumentSaveTitle,Value,(),GetInterviewTitle(),,OnlyWhenEmpty)»
On the interview screen users will be shown a field called DocumentSaveTitle, and it will be populated with the title of the template. Should you use this method, remember to save your templates with a title.
Saving of datasets:
Now set a path and name for your datasets. It makes sense to save assembled documents associated with matters into iManage, and datasets into XpressDox (the system which understands xml datasets).
In this example all datasets are saved into a Datasets folder in your XpressDox account. The name of each dataset will be the MatterID e.g. PL001.xddata.xml. You could take this one step further and use IncludeFileData to include any existing saved data on your templates. «IncludeFileData(.\Datasets\<MatterID>.xddata.xml,Refresh,,,FileExists(concat(‘.\Datasets\’,MatterID,’.xddata.xml’)))»
Now learn about setting profile properties in your template, or run your templates.