Skip Ribbon Commands
Skip to main content

Process models in ContactsLaw consist of milestones with various entry points and work items. You can control which work items are created by specifying one or more conditions based on properties of the file, documents, contacts and more.

These conditions can also be used in document workflows (to determine whether a step is performed or not) and document templates (to control which enclosures are included).

Types of conditions

  • Bill - Whether the file has been billed or not.
  • Conflict check - Whether party or representative conflicts have been detected on the file.
  • Date* - Compare the value of a particular date on the document to an absolute date or relative duration.
  • Debtors balance - Compare the debtor balance on the file to a certain amount.
  • Document - Check for the presence and status of a particular type of document.
  • Document contact* - Perform a variety of checks based on the contact(s) in a particular role on the document.
  • File contact - Perform a variety of checks based on the contact(s) in a particular role on the file.
  • File contact type - As above, but allows you to refer to contacts by type (client, bill-to, liaison, etc) instead of by role.
  • Prompt the user - Displays a prompt and allows the user to answer a Yes/No question.
  • Representative - Perform a variety of checks based on a file contact's representative.
  • Template mapping field - Test the result of a document template field mapping. (Note: Fields under the 'Document' heading are meaningless when used in a condition for a process model)
  • Workgroup field - Test the value of a workgroup field.
  • File Activity - Test whether a file has had any of the following within stated period:
    • ​​Bills issued (according to issued date);
    • Journals and fixed charges recorded;
    • Transactions (both General and Trust) according to transaction date; or
    • Documents registered (using document date).
* - Available in document workflows only.

Combining conditions

When you add multiple conditions, you can indicate whether a condition and the one preceding it must both be true ("AND") or if either can be true ("OR"). These boolean operators are evaluated from left-to-right. All conditions are evaluated regardless of the intermediate result ("short circuit" evaluation is not used). 

When there are no conditions specified, the work item will always be created.