Event
ContactsLaw records noteworthy events that occur on various items, such as matters, documents and transactions.
Each time an event occurs, the following details are recorded on the item:
- The type of event
- Date and time when the event occurred
- The member to whom the event can be attributed
In the Desktop App, events are shown on the History tab/view.
Triggering Events
Events typically occur when the state of an item changes; for example, when a document is catalogued or when a transaction is processed.
Some types of events trigger according to specific criteria; for example, when a potential conflict of interest is detected on a matter.
Generally, events cannot be triggered manually.
The same type of event can occur multiple times on a given item; for example, an invoice may have multiple finalisation events owing to redrafting.
When an event is triggered:
- A record of the event is stored on the item (in most cases, see below for exceptions)
- Entry points may cause processes to start in response to the event
Implicit Events
There are situations where a record of an event may not be stored on the item.
If multiple consecutive events occur as a result of the same action (e.g. a transaction is authorised as a result of being processed by an authorised member), then the intermediate events are not recorded.
Some types of items (e.g. checklist items) do not separately record events because they can be inferred from the item itself.
Even if a record of the event is not stored on the item, entry points are still triggered.
Custom Events
Subscribers can define custom event types for various items, which are triggered by rules on processes.
They can be used, for example, to:
- Permanently record on the item whenever a particular process is performed
- Identify particular scenarios that are noteworthy to the business
- Trigger other processes (consolidating and simplifying processes)