A server is meant to be hosted in a special facility.
A datacenter is temperature controlled, physically secure, with fire detection, backup power, redundant network connections, air conditioned etc.
A server is a special computer with built-in redundancy.
Servers feature two sets of power supply, several sets of hard disks, multiple network connections.
The optimum value of the software is realised when the software is available 24/7 from any location – home, office, courtroom
A dedicated server gives the best performance as the installation avoids unnecessary software installations and running processes.
Additional compatible software can be installed in the server at little or no additional running cost
Automated off-site backups are available when the server is online and will survive office document losses.
This demo shows how a conveyance is created and thereafter how to submit work.
A conveyance is structured as a set of documents and events that need to tracked. mLaw does this by listing all the documents that are required for a conveyance. As the documents become ready, they are added to the conveyance (as conveyance work).
Specific events are also created to track certain milestones of the conveyance process. Event creation is not shown in the demo but is very similar to event creation in the court case demo.
This playlist demonstrates the process of creating a court case, assigning users, submitting work, associating events and adding legal fees.
The process of assigning users, submitting work, associating events (dates) and adding legal fees is quite similar to what is done for other matters in the system i.e. conveyances, contracts and legal opinions.
Some of the actions shown e.g. creating a court case and submitting work require approval and therefore once the initial user (clerk1) submits the form, the approver (lawyer1) logs in to approve the pending request. This is a 2 level approval but can be customized to any number of levels e.g. clerk to supervisor to manager to partner.
Creating event types, status types, adding users etc is not covered by the demo but the process is intuitive. Most of these data can also be imported into the system during implementation.
Individual videos can be viewed on YouTube.
Your comments are most welcome.