Priority Table (79)
Priority MDO list item table. Priority list table. Used with appointments; low, high.
Fields
| Name | Description | Type | Null |
|---|---|---|---|
| Priority_id | Primary key | PK | |
| name | The list item | String(239) | |
| rank | Rank order | UShort | ● |
| tooltip | Tooltip or other description | String(254) | ● |
| deleted | 0 -> record is active 1 -> record is ‘deleted’ and should not be shown in lists | UShort | ● |
| registered | Registered when | UtcDateTime | |
| registered_associate_id | Registered by whom | FK associate | |
| updated | Last updated when | UtcDateTime | |
| updated_associate_id | Last updated by whom | FK associate | |
| updatedCount | Number of updates made to this record | UShort |
Indexes
| Fields | Types | Description |
|---|---|---|
| Priority_id | PK | Clustered, Unique |
| name | String(239) | Unique |
Relationships
| Table | Description |
|---|---|
| appointment | Tasks, appointments, followups, phone calls; and documents (document_id != 0). An appointment always has a corresponding record in VisibleFor specifying who may see this. |
| associate | Employees, resources and other users - except for External persons |
| PriorityGroupLink | User group link table for Priority, for MDO item hiding |
| PriorityHeadingLink | Heading link table for Priority, for MDO headers |
Replication Flags
- Replicate changes DOWN from central to satellites and travellers.
- Replicate changes UP from satellites and travellers back to central.
- Copy to satellite and travel prototypes.
Security Flags
- No access control via user’s Role.