Overview
Clio Operate provides integration with iManage as a DMS via the iManage REST services.
The connection is made using an OAuth client credentials flow where Clio Operate requests an access token from iManage using a client Id and Client Secret configured in an iManage “Application”.
At a high level, the steps required to enable iManage integration are:
- Create a Clio Operate user account in iManage
- Create a new “Application” in iManage for Clio Operate
- Configure required workspaces in iManage
- Configure the iManage Linked Service in Clio Operate
The following pages describe how to establish integration between Clio Operate and your iManage instance in more detail.
Pre-requisites
Clio Operate needs to be able to see your iManage REST API
There are a couple of options for this.
- If you are on Cloud iManage and do not have any IP whitelist/blacklist on access to this instance, then Clio Operate will be able to see the iManage REST API.
- If you have an on-premise iManage installation then:
- The server component needs to be at least iManage 10.2
- The REST API needs to be either exposed to the internet with appropriate IP whitelist/blacklist
- OR
- an Azure Site-to-Site VPN can be created between your Clio Operate instance and you on-premise iManage servers (note there is an additional operating cost for this VPN).
Clio Operate needs to use your iManage workspaces to store its own documents
Clio Operate provides some areas of functionality where it requires access to document storage. While a different DMS can be used to store these documents, it is often best to use the same DMS for all documents.
For the below, it is possible to configure a single workspace for all of these functional areas, one workspace for each functional area or any combination of these. We have provided a structure that is commonly used.
| Area / Repository | Function | Suggested structure |
|---|---|---|
| Document Templates |
Used to store and manage the document templates, email templates and notification templates used in Clio Operate. Required if: you are using Clio Operate to generate documents |
Workspace: Shared Administration Folder: Document Templates |
| Data Uploads |
Used to store any CSV data uploads while they are being processed into Clio Operate Required if: you need to upload CSV data into Clio Operate using the Excel/CSV data upload feature |
Workspace: Clio Operate Administration Folder: Data Uploads |
| Inbound Email |
Used to temporarily store the attachments of inbound emails prior to them being filed against existing matters Required if: you plan to use Clio Operate to monitor team email addresses and process inbound email |
Workspace: Clio Operate Inbound Email Folder: Attachments |
| Instructions |
Used to store documents relating to instructions (aka Enquiries / Leads) prior to them being converted to matters. Required if: you plan to use Clio Operate to process instructions work types |
Workspace: Clio Operate Instructions Folder: Documents |
| Service Requests |
Service Requests are commonly used in Clio Operate client portal implementations, providing a mechanism for client users to request action. Required if: you plan on using client portal service requests and wish to have documents associated with these. |
Workspace: Clio Operate Service Requests Folder: Documents |
| Scanning |
Enterprise scanning systems can target storing scanned documents in a DMS. Clio Operate can be configured to look at the location for scanned document, allowing users the ability to. [Similar functionality can be enabled for inbound post] Required if: you want to use Clio Operate to file scanned documents in the DMS to existing cases. |
Workspace: Clio Operate Inbound Scanning Folder: Documents |
| Client Documents |
Clio Operate client portal implementations often require a general area where documents can be provided for specific clients. These may be terms of reference, usage guides etc. Rquired if: you plan on having an area in your Clio Operate client portal where client users can access general documents. |
Workspace: Clio Operate Administration Folder: Client Documents |
Clio Operate needs to understand your iManage configuration
Clio Operate provides a view of the iManage Workspace that it is configured to locate.
There are two main mechanisms that Clio Operate uses to locate an iManage workspace. These mechanisms are configurable by repository and work type.
Default Search
In this mode, Clio Operate will search for the workspace using the name it resolves from its configuration. e.g.
workspaceResolverConfig: “Clio Operate Document Templates”This will search iManage for a workspace with a Title = “Clio Operate Document Templates”
- The first workspace that matches will be used
- The contents of the workspace will be seen in Clio Operate.
workspaceResolverConfig: “[workitem.title]”You can use Clio Operate data composer queries in this configuration.
If we have a work item with a title of “CASE101: John Smith vs. Jane Doe” then Clio Operate will resolve this title and search for a workspace matching this in iManage.
- The first workspace that matches will be used
- The contents of the workspace will be seen in Clio Operate
- If no matches are found, Clio Operate will show an error.
Advanced Search
In many instances, searching for a matching title isn't practical. This works for general workspaces that Clio Operate might use for document templates, or storing inbound email attachments but when we are looking for matters it is often more complex.
Advanced Search lets you configure several matching tags to search on.
We commonly see configurations like this;
workspaceResolverConfig: “custom1=[workitem.client.reference], custom2=[workitem.reference]”This corresponds to the common approach of using custom1 and custom2 in iManage to denote the “Client Reference” and “Matter Reference”, which are often seen combined - i.e. 12345.00001
Clio Operate needs to be able to encrypt your tokens
OAuth tokens consist of Access Tokens (AT) and Refresh Tokens (RT). In iManage you will configure the lifetime of these tokens.
When you ‘link’ a user account to iManage, Clio Operate will receive a response containing the AT and the RT.
Clio Operate will encrypt and store these tokens. This is done using certificate encryption, combined with a system admin provided ‘seed’. The seed is a passphrase of over 100 characters, which is provided in system setup.
You should ensure that the encryption feature is enabled and configured in Clio Operate. To do this:
Go to Launchpad > Modeller > Global Features. Search for “Encryption” and toggle on Include Advanced.
If the Encryption feature card has a red border, you must configure the feature. Please provide a passphrase or discuss this with your Clio Operate implementing team. Configure that by adding a key phrase, which is then used to encrypt the linked service data. Give it a nice long Key phrase and ensure that it is not changed once it is added.
Once configured, the feature should look like the image below:
