Case Status
Log In


Worksite Lookup
  • RSS Feed

Last modified on 9/1/2017 11:08 AM by User.


Worksite Lookup

Worksite Integration:

Run as administrator – KAPPRISIWPRINTINSTALL.bat which adds the correct entries to the registry.

This is in C:\Program Files (x86)\Kutana\Kappris folder.

In the config.ini. file in C:\Program Files (x86)\Kutana\Kappris folder add/amend the following:



#Caxton Visible=True
#Caxton Show Progress=True
#Caxton Always Keep=True
#Caxton Wait To Proceed=True
#Show Standard Driver UI=True
Profiling Active=False
Profile Log File=C:\KapFiles\Logs


[DMS Info]

Document Name Format=[DESCRIPTION] [MATTER] . [CLIENT]
Document ID Pattern=(\d{1,8})[_v](\d{1,4})
Document Lookup Pattern=$1_$2
Overwrite Name=True

In DEBUG above, the Profiling entry is used for creating a log using Codesite. Set to TRUE to turn on. You will also need to use a modified Kupris.dll file (attached) which contains extra logging info.

For an ini file look up for testing purposes, use the Provider and Connection strings with # in front instead of what is currently in use

NRPORTBL is the local cache which is quicker to look at and should contain the correct document relating to the ID we are looking up (the same ID can be used for documents in different libraries)
USER will use the windows account currently being used if not specified.

To check the settings above are correct, you can examine the contents of the .prf file that is created with each print job and when Word is opened.
Print a Word doc from Worksite and then look in c:\nrportbl\active\USERINITIALS and look for your recent print. It will have an associated .prf which when opened in Notepad will show all the relevant field names and how they are formatted such as DESCRIPTION, CLIENT, MATTER. You can change what is used for the file name using any fields available in the .PRF file.

Expanation of new Document ID Parameters to deal with the new naming convention in iManage which uses 'v' in the doc name instead of '_'. The new expression deals with both eventualities.

Consider section [DMS Info]

If we change an entry:
Document ID Pattern=(\d{1,8})[_v](\d{1,4})
This creates two groups that can be referred to as $1 and $2
If the document name is #13327689v31 Blah blah blah.docx this pattern will find 13327689v31 and $1 will refer to 13327689 while $2 will refer to 31.
A new entry Document Lookup Pattern can then be used to reconfigure this so that it uses an underscore "_" when it tells the DMS lookup facility to find the document.

Document Lookup Pattern=$1_$2
Using these two entries in this way, we can find different formats of embedded document ID but then convert them to the same single format for use when searching.
A FURTHER entry is used to provide enhanced functionality but preserve current behaviour.

Overwrite Name
This will cause the document name will be entirely replaced with the information returned from the DMS.
If this value is missing or False only the embedded document ID within the doc
ument name will be replaced with the information from the DMS.