...
Type | Functional description | Error message | Comments | |
---|---|---|---|---|
1 | Delete (status) | Users can apply a status of "delete" to a particular record, which would mean that the record would be deleted from the front end Example: People (Sensitive Data / Manage Record / Status) | No error message displayed | |
2 | Inactive (status) | Users can apply a status of "Inactive" to a particular record or reference data field, which would mean that the record or field is made temporarily unavailable Example: People records (People / Sensitive Data / Manage Record / Status) | No error message displayed | |
3 | Trash can | Users can click on the trash can next to a field and permanently remove data from TIS Example: Placement record (People / Placements / Placement list) | "Are you sure you want to delete?" displayed | |
4 | Minus | Users can click on the minus sign next to a field and permanently remove it from TIS Example: Curricula (Programme / Curricula) | No error message displayed | |
5 | X | Users can click on the X sign next to a field and permanently remove it from TIS Example: Roles field (People / Sensitive Data / Manage Records / Roles) | No error message displayed | |
6 | Dates from/to | Users can specify an end date, which would make the related record or fields Inactive after that date has elapsed Example: Post funding (Posts / Post record / Funding) | No error message displayed | |
7 | Archive | Not currently implemented in TIS | N/A |
- Delete (status)
- applied at both record and field level
- this acts as a soft delete
- removed the field from the front end
- does not de-link where applied
- removes link ability for new scenarios
...
Where is this used? | Comments | ||
---|---|---|---|
ProgrammesRecords: People, | |||
Posts | ,Field level: | ||
Programmes |
2. Inactive (status)
- can be applied at both record and field level
- impact of applying this to field being used in a current record, is
- filtering may need to be applied to view the record in a list page
- drop downs for reference tables will not display anything that has been made with an inactive status
- records containing inactive data will not be flagged, but editing my present errors
- assessment records may become legacy, and no changes will be possible once this kicks in
...
Where is this used? | Comments | |
---|---|---|
Programmes | ||
Posts | ||
Programmes |
3. Trash Can (button)
- this functions as a hard delete
- removes existing linkages with records and other fields
...
Where is this used? | Comments | |
---|---|---|
People: Placement | ||
People: Programme Membership |
4. Minus sign
- this functions as a hard delete
- removes existing linkages with records and other fields
...
Where is this used? | Comments | |
---|---|---|
People: Qualifications | ||
People: Programme Membership | ||
Posts: Other specialties | ||
Posts: Sub-specialties | ||
Posts: Other grades | ||
Posts: Other sites | ||
Posts: Programme names | ||
Programme: Curricula |
4. X
- this functions as a hard delete
- removes existing linkages with records and other fields
Where is this used? | Comments | |
---|---|---|
People: Roles |
4. Dates from / to
- this functions as a hard delete
- removes existing linkages with records and other fields
Where is this used? | Comments | |
---|---|---|
People: Registration dates | ||
People: Inactive date | ||
People: Programme membership |
<data flows>
To Be
In order to consolidate the way that the concept of deletion is used across TIS, the following rules should be applied:
...