This is a auto-generated Article of all your definitions within the glossary.
Glossary
This is a auto-generated Article of all your definitions within the glossary.
-
Aspect
Aspects are a particular view of information in the system. They make up the components of the blade user interface forms within the system, and they can either be a section of the form, or a navigation bar leading to another blade.
-
Banding
Banding is a grouped profile measurement of scorecards. It describes ranges of values that define a band, e.g., low band: values 1 to 3, medium band: values 4 to 5. etc.
-
Blade
Blades pop out from the right-hand side of the screen, follow a common format, and allow you to keep the context of where you were working while you view the blade.
-
DMS
Document Management System - This is where documents, emails, and other files are stored, and it could be SharePoint, iManage, or another system your ShareDo environment is integrated with.
-
ETL
In computing, extract, transform, load (ETL) is a three-phase process where data is extracted, transformed (sanitized) and loaded into an output data container.
-
Form builder
A special aspect type that you can use to add a custom data capture form to a blade. The aspect is the container in which your form is placed. Sharedo configures connections for saving, so you don't have to.
-
Instruction
Instructions are the primary container for processing inbound instructions. Just like any other item of work in ShareDo, they can be specialised to meet specific processing requirements. Using instructions, you can model different data and processing requirements.
-
Launchpad
The launchpad menu is customisable and acts as your toolkit to create work items, perform admin tasks and modelling, and create activities.
-
Matter
Matters are the primary container for managing legal cases throughout their life cycle. The matter container provides all the tools and processes to facilitate efficient case management while supporting compliance with regulatory and business protocols. When an instruction is converted, it becomes a matter.
-
ODS
The Operation Data Store is a repository of entities that can be shared across cases - people, teams and orgs. For example, people can (and should, to keep their details consistent) be defined once and referenced from all cases that they are involved in. These entities can have related data, such as contact information and network connections (employed by X), that remain the same regardless of the case that they are on. Vehicles, however, are "raw" participants that don't need to be shared across cases. They don't have related data as such, only participant data relating to the case itself (like occupants, damage, etc).
-
ODS entity
An entry in the ODS, stored centrally in ShareDo. It could be a participant type, a party type, or a participant. Data captured against the entity can be surfaced across different work types or areas within ShareDo.
-
Participant
The entity that participates in a case. This could be a person, legal service provider, client, expert, and others.
-
Participant role
What role the participant plays in a piece of work. For example, a person who raises a complaint will be given the Role of Complainant. Other typical Roles include Employer, General Practitioner, Member of Public.
-
Participants
The entity that participates in a case. This could be a person, legal service provider, client, expert, and others.
-
Participant types
A category of participants which may be further organised into party types. E.g., an organisation, person, team, title (real estate), user, or vehicle.
-
Party type
A sub-category of the participant type, e.g., a court, client, or expert, is a sub-category of the organisation participant type.
-
Party types
A sub-category of the participant type, e.g., a court, client, or expert, is a sub-category of the organisation participant type.
-
Persona
Categorisations of users. An internal user of your organisation is one persona, and a B2B customer is another. The look and feel of workbenches and the content presented are defined per persona.
-
Portal
The central area of the screen and usually the place you are working or looking at information.
-
Proceeding
ShareDo provides a specialist work type for litigation. The proceeding modeller is used to configure litigation for different court tracks and jurisdictions.
-
Radar
An interactive contextual widget at the top of your ShareDo portal screen (beneath the global navigation bar, and action bar) that provides insight on your current work.
-
Scorecard
A scorecard is a way of measuring a matter characteristic based on any number of (weighted) input variables.
-
sharedo (database context)
A 'sharedo' in the context of the database, is any ShareDo application data that has a state, type, or permissions.
-
Statement of Work
In ShareDo, matters (and instructions) are performed under the control of a Statement of Work (SOW). The SOW will define, for a given set of matters, items such as the SLA, commercial terms, and security/processing teams.
-
Striping
Enables you to control what data or content is displayed in the application based on the context. It allows you to tailor the user interface content based on the user.
-
Tag
A system placeholder for information used in various places within ShareDo. Most commonly used in document generation.
-
Tags
System placeholders for information used in various places within ShareDo. Most commonly used in document generation.
-
Task and Activities
Out of the box, ShareDo provides several core task building blocks. Examples include document automation, contact (email, fax, SMS), appointments, telephone calls, and the like. Similarly to all other work types, these can be extended for specific processing needs, called from workflows, plans, etc.
-
Workbench
A collection of views on work items, where those work items/matters can be reviewed, managed and actioned.
-
Workflows
In ShareDo, workflows can be as automated or assistive as you like. They can guide or aim to replace case handlers as is appropriate for your work management style.