Tutorial Videos

Tutorial videos are available here.

Knowledge Base

Visit our User Forum for discussions & solutions

Running templates and saving to NetDocuments – XpressDox

Click here for an overview of saving documents into NetDocuments.

This is Step 4 (the final step) in the process of saving documents to NetDocuments.


Upload your DocumentAssembly.config.xml file

Now that you have made changes to your config file, you need to upload that config file. It helps to have the same file structure on your development environment as you do on your Cloud environment. If you will be using the Desktop version, then there is no need for any uploading.

Ensure that you upload your config file to the correct folder location (remembering that settings are applied to the current folder as well as all sub-folders). Applying the Foreign File System to the highest level means that all templates run from any location will be able to communicate with NetDocuments.


Running templates in XpressDox environment

You are now ready to run templates. At this point you can simply run templates from your XpressDox instance. Enter in your ClientID and MatterID on the interview, and assembled documents will be saved into NetDocuments.


Running templates in NetDocuments

Embedding your XpressDox instance, or even a specific interview, in NetDocuments is an optional step but it does mean that if your users are used to working exclusively in NetDocuments they now get to stay in one environment and run their templates all from one place. Additionally, matter context data elements can be injected into the interview without users having to look up that information!


To embed your XpressDox instance directly into a NetDocuments workspace, go to the Workspace, click on the Overview tab and click on “Add web page” from the Matter drop down list.


Add a label for your new Web page, change the height and paste in your URL. Note the MatterID and ClientID in the URL. Passing in these parameters means that that the MatterID and ClientID will be known by the interview. MatterID is the data element name and then select “Insert Merge Code” to insert the corresponding NetDocuments code. Repeat with the ClientID. And click Save Changes.


The URL shown in the above screenshot is broken down as follows. Note how it changes depending on if your firm uses Single Sign On in XpressDox.



WITH XpressDox SSO:{!Workspace.Base.Attribute.Key}&ClientID={!Workspace.Parent.Attribute.Key}
  • where [] represents your XpressDox instance
  • and [] is the domain name for your SSO.



Send your user directly to a specific template:{!Workspace.Base.Attribute.Key}&ClientID={!Workspace.Parent.Attribute.Key}&templateId=2837492382938
  • where [] represents your XpressDox instance;
  • [] is the domain name for your SSO; and
  • templateId=2837492382938 is the template identifier of the template.
You can read more about template identifiers here.



Although not as seamless an integration, it is possible to integrate XpressDox into NetDocuments without the use of SSO. Your URL would look like this:

WITHOUT XpressDox SSO:{!Workspace.Parent.Attribute.Key}&MatterID={!Workspace.Base.Attribute.Key}
  • where [] represents your XpressDox instance


If you have embedded the whole XpressDox instance, it will now be available in the Overview tab. Select a template to run it. Or users can click on the template you have embedded, and be taken directly there without the need for navigating around.



And note how ClientID and MatterID have been populated by NetDocuments! Here is the assembled document in XpressDox.


And the document has been filed away in the correct place in NetDocuments, by ClientID – MatterID.


In this case the document was filed away into a folder called NDAs because there is a config file in the NDA template folder specifying that templates run out of that folder should go into N:\[<ClientID>]:[<MatterID>]\NDAs.
In this example, the config file at the highest level contains the Foreign File System. Then there is a config file at each folder level containing the Standard Folders path. When a template is run from any folder, settings are applied from the config in that folder as well as any configs in folders higher up.
This is not a prescriptive way; XpressDox is very customizable and you can decide how you want to structure your folder structure. Just make sure that the Foreign File System is accessible by all folders, and that all folders access N:\[<ClientID>]:[<MatterID>] in some way.