Help - Training
|
|
Help - Training |
|
The objectives for this training guide are:
- Understand the matter table,
- Understand the process table,
- Understand the task table,
- Understand the field table,
- Understand process management and reporting,
- Understand task management and reporting,
- Understand task dates, and
- Understand field repeatability
For the mortgage servicing industry, a row in the matter table is used to represent a mortgage taken out on a property address. Included with each matter is a client, client loan number, date opened, date on hold, date closed, property address and a reference name. The reference name is used to represent the name of the primary party; e.g. the "Jones" file.
A process should generally be viewed as a series of tasks which comprise an invoice to a client. If the work being done on a matter "belongs" on a new invoice, it generally makes sense to add a new process.
A task should generally be a unit of work. If the task has explicit costs associated with it (ordering of a title, for instance), it can be export to an accounting system. Tasks are associate with a process, and exception tasks can be added to a process as needed. They can be defined with repeatability (see fields), but this is currently not enforced.
Fields are units of information, other than the information covered in matters, processes and tasks, which need to be tracked by an office. Each field can be used by (displayed in) one or more tasks. They are defined with repeatability as follows:
- Once per matter: the field may have only one value for the entire matter (e.g. Investor Loan Number)
- Once per process: the field may have one value per process, but may change when adding a new process (e.g. Foreclosure Sale Date)
- Once per task: the field may have a different value in each task. (e.g. Previous Sale Date in a continuance task)
Understanding the behavior of fields is critical to designing documents correctly.
Welcome |
Users |
Business |
Managers |
Documents |
Lookup |
Administrators
|