...
Table Name | Description |
actions | In the client’s system these may be referred to as “matters” or “cases” depending on the admin setting for action alias. This table lists all the action names along with meta data like date created, action type, current step, last activity, etc. |
action_participants | The names and roles of all the parties linked to an action |
action_types | The names of the action types (workflows) defined in the system e.g. Litigation, Estate Planning, etc |
action_participant_custom_data_values | The contents of any custom data fields you have created for contacts that have been saved to an action |
client_billing_invoices | A list of all billing invoices along with amounts, status, etc |
client_billing_invoice_allocations | How the fees and expenses in the billing invoices have been allocated to the fee earners |
contacts | All contact records (name, address, etc) linked to actions and time entries |
participant_custom_data_values | The contents of any custom data fields you have created for contacts that have been saved to the contact record |
| participant_kpis | KPIs for each user (as set via Accounting > Accounts > KPIs) |
participant_types | A list of all the participant (contact) types defined in the system e.g. Lawyer, Client, Defendant, Court, Judge, etc |
time_entries | Timesheet data. |
dc_{A}_{B} | “Data Collection” tables. Aseparate table is created for each of the custom data collections defined for each action type (workflow). The naming convention is “dc_” (“data collection”) followed by the matter type ID (A) followed by the data collection name (B) (in lower case with underscores for spaces). For example: the table name for a data collection called “Engagement Info” for action type ID 6 would be “dc_6_engagement_info”. |
...