Cache

A special high-speed storage mechanism. The TeamConnect application server has its own user interface caching mechanism to store the screen designs and other user interface data accessed by the application. You can clear the TeamConnect user interface Cache by either re-starting the application server or by clicking Clear Cache in the User Interface Settings screen of the System Settings on the Admin tab.

Browsers have their own memory caching mechanisms that can be cleared by closing the browser.

Calendar

A special search results display type available in for search views only in the Appointment object definition. It displays scheduled appointments in a day planner layout.

Cascading Security

The transferring of parent projects' record-level security, automatically in a waterfall fashion, to their related records. This is done on the Security tab of only custom object definitions.

Category

Items in the user interface that are associated with specific groups of fields displayed in a record.

By adding or deleting categories in a record, you can display or hide the associated sections or fields in that record. In some cases, you might need the user rights to view specific categories and the custom fields belonging to them.

Category Security 

The Rights to the object's categories and their custom fields. This is the second level of security, after the object level. All rights assigned at this level take effect only if the access to the object itself is granted.

Category-level rights add more granularity to the object-level rights. A user might have access to the object, but you can still control access to the organization-specific information stored in the custom fields and displayed in custom blocks.

Check In or Out

A way to manage files that are uploaded to the Documents screens so that only one person at a time can edit them. If a file is checked out, no other users can edit the file. When the user is done editing and checks the file in, it becomes available for check out.

Child

Hierarchical relations where one (parent) item can have multiple (child) items, whereas each child item can have only one parent. Typically, parent-child relations can be established between Custom Objects in their object definitions. For example, one Claim can have multiple Features, one Feature can have multiple Sub-features, and so on.

The term "parent" can be also used with reference to the custom object that has Embedded Objects defined for it.

Categories can also have parent-child relations.

Child Record

A record that has a parent record. Records can have hierarchical relationships between records. One (parent) record can have multiple (child) records, whereas each child record can have only one parent.

Child records might be required to have a parent. However, parent records are not required to have child records.

Categories can also have parent-child relations.

For more details, see "Parent and Child Accounts" on page 87 and "Parent and Child Projects" on page 110.

CLASSPATH 

An environment variable or argument set on the command-line that tells the Java Virtual Machine where to look for user-defined classes and packages in Java programs.

COD 

Custom Object Definition

Command Line

The command line is a text-based interface that lets you interact with your computer by entering commands, which it then sends to the operating system to execute.

Comparative Dashboard

The Comparative Dashboard shows the performance of a law firm compared to other selected law firm(s) with InvoiceIQ metric overviews using widgets. The Diversity Comparison dashboard compares the distribution of hours and fees by gender or race of one law firm with a selected law firm or group of law firms. This helps to see whether the diversity goals specific to the organizations are achieved or not.

Concurrent Update

A Concurrent Update refers to a situation in which multiple users or processes attempt to modify the same data or record in a system at the same time. This can lead to conflicts, data integrity issues, or overwriting changes, necessitating mechanisms like locking or version control to manage and ensure accurate updates.

Condition

A value that you select for a qualifier in a Rule. For example, a condition could be an assignee role, a phase, a number of days from when the Record was opened or closed, and so on. See also Attribute and Qualifier.

Contact

Individuals or organizations that conduct business with your organization and in one way or another are involved in the records with which you work. For example, staff, claimants, opposing parties, witnesses, agencies, vendors, outside counsels, and so on can all be described by contact records. You specify Categories to indicate the type of contact.

Contact-Centric Projects

Projects that are associated with and revolve around a specific contact without which they cannot exist. For example, an insurance claim record cannot be created without specifying an insured contact.

Within a contact-centric project, the contact record is displayed as a single hyperlink. It is created through a search module field and displayed in the general information section of the project.

Contact Group (Address Book)

A System Object definition that is intended to allow end Users to organize their Contact records together. Users can create groups of contacts with whom they frequently interact, so that their phone numbers are readily accessible when needed. The members of contact groups who are also Users can be added as attendees to appointments.

Contact Groups are called Address Books in the end-user interface.

Contact Object

A record in TeamConnect that stores details about people or organizations (like address or phone number).

Currency

The type of money used in transactions (e.g., USD, EUR).

Currency Code

Abbrevation of the Currency used in Invoices, Rate Requests and other financial functionality.

Currency exchange rate

Rate at which the currency exchanges in Invoices, Rate Requests and other financial functionality.

Currency Name

Name of the Currency used in Invoices, Rate Requests and other financial functionality.

Custom Action

An action performed by a rule in TeamConnect that is defined in a JavaScript or Java class file. Custom Actions can do a wide range of functions - anything that is possible with Java or Javascript.

Custom Apps

Custom apps are developed specifically for a particular client or organization. They are tailored to meet clients' specific needs, requirements, and preferences.

Custom Block/Rule

A Custom Block/Rule allows users to create specific conditions or rules according to their organization's needs.

Custom Fields 

Fields that are created on required basis and can be added, removed, and customized. They are typically defined by naming the field, specifying its data type, and any other necessary parameters. Custom fields can be created per system or custom object. These fields allow you to meet the individual needs of your organization. 

Custom Objects

Objects created for your organization. Unlike System Objects, they do not come standard with TeamConnect. They are created by your TeamConnect developer. Custom objects can have names used within your organization for records or files, such as matters, and policies. Within this documentation, custom objects are referred to as Projects.