Scenario

You perform conflict checks across multiple systems in your organisation.

For example:

• You are migrating from one case management system to another and need to conflict check across both during the transition
  or 
• You have multiple specialised case management systems in addition to Clio Operate.

Recommended Architecture

Clio Operate cannot typically access all of the systems required to perform a conflict check across the entire organisation, meaning that a client-owned conflict check service is likely to be required.

Even if Clio Operate can access all external systems, there is no functionality to combine results from other systems with Clio Operate’s built-in conflict check process.

In addition, other systems require the ability to perform conflict searches of Clio Operate records. Without a central service for conflict checking, all logic must be duplicated across all systems involved in the check.

With that in mind, we recommend you build your own a standalone conflict check service that can collate the results from each system (including Clio Operate) into a single process:

 

Recommended Process

A Clio Operate workflow should generate a ‘Conflict Check’ task (we recommend using a custom task work type configured to capture related data, use phases, etc.). The workflow would call the client’s API to trigger the conflict check process.

The service should:

• Check each case management system in turn (including Clio Operate)
• Generate a document with the results of the conflict check
• Call the Clio Operate Public API to upload the document to the task (this will be saved in the document repository for the parent work item. e.g. the matter)
• Call the Clio Operate Public API to set the phase of the conflict check task based on the result (‘Passed’, ‘Needs Review’, etc.)

A Clio Operate workflow can respond to this phase change, and instigate any follow-up process. For example, referring the task to a compliance team for review.