Context:
The previous page describes the various mechanisms by which a user can delete a field/record on TIS currently, and provides suggestions as to how this might be tackled in future (with re-work on the FE and BE), however, there is no downstream review of impact. This page gives an overview of the following
...
In conclusion, deletion could continue to be applied by status, however each status would imply a particular action. These are described below:
...
- the field/form cannot be viewed on the TIS UI
- the field/form remains in the Back End of TIS to allow it be shared with NDW and retrieved if required (until it must be filed or archived)
- the field/form is sent to NDW as a "deleted" value
Archive (AR 28/08: Solutionising? This status does not exist at the moment and the scope of Archiving as a requirement has not been reviewed yet)
- the field/form cannot be viewed on the TIS UI
- the field/form cannot be viewed in the TIS back end
- the field/form must be stored in an archived location (TBD)
- the archiving process is automated (TBC)
- archiving should be read only (snapshot), without requirement for reference values
...
This will need to be updated once "missing" fields have been agreed for the TIS UI (see here: NDW UAT feedback)
Impact Analysis
The fields listed are only those displayed in the TIS front end:
...
RolePermission
- whole entry status can be: INACTIVE / DELETE / ARCHIVE on the FE
- Should be stored against a relevant person ID (tbc) when deleted or archived
...
DELETE
ARCHIVE
...
- deletion will remove the role from the FE, but retain the it in the BE
- permissions will be removed to the user on login
- a role must be assigned to any user who needs to use the system
- roles should be archived against a person record (i.e. for users who are also managed within TIS)
- roles should be archived against users (i.e. for users who are not managed within TIS)
...
- the permission is removed where the role is removed
...
Role
- whole entry status can be: INACTIVE / DELETE / ARCHIVE on the FE
...
INACTIVE
DELETE
...
- inactive will remove the role from being applied in the FE
- delete will remove the value from the table
- delete will remove data from forms where the role is in use
This is held in Keycloak currently, this is only relevant where role/permission management moves into TIS (as reference data)
Assumption is that reference data archiving is not necessary
...
UserRole
- whole entry status can be: INACTIVE / DELETE / ARCHIVE on the FE
- Should be stored against a relevant person ID (tbc)
...
DELETE
ARCHIVE
...
- usernames are mandatory so at least 1 is necessary for a user to be active in TIS
- delete will remove their ability to login to TIS
- archive will retain a copy of the username details
...
DELETE
ARCHIVE
...
- deletion will remove the role from the FE, but retain the it in the BE
- permissions will be removed to the user on login
- a role must be assigned to any user who needs to use the system
- roles should be archived against a person record (i.e. for users who are also managed within TIS)
- roles should be archived against users (i.e. for users who are not managed within TIS)
...
This is held in Keycloak currently, this is only relevant where role/permission management moves into TIS
Is this data linked to the data held in the RolePermission or is it held separately? If so, then would the status of one or both instances of a like-role need to be altered?
...
PersonalDetails
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
TrainingNumber
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
GdcDetails
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
INACTIVE
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
GmcDetails
...
)
...
DELETE
ARCHIVE
...
INACTIVE
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
ContactDetails
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
RightToWork
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
Qualification
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
Comment
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
PersonTrust
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
PersonOwner
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
RotationPerson
- entry status can be: INACTIVE / DELETE / ARCHIVE
...
DELETE
ARCHIVE
...
Rotation
- Whole entry status can be: INACTIVE / DELETE / ARCHIVE
...
DELETE
...
INACTIVE
DELETE
ARCHIVE
...
RotationPost
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
PlacementSupervisor
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
TBC
...
TBC
...
Programme
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
INACTIVE
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
Placement
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
Curriculum
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
Post
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
INACTIVE
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
PostFunding
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
Specialty
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
INACTIVE
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
ProgrammeMembership
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
Assessment
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
INACTIVE
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
AssessmentDetail
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
AssessmentOutcome
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
Revalidation
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
Reference Tables - these have been summarised since the rules should be similar in the majority of instances (some have other values which will be impacted if the below rules are adhered)
- entry status can be: INACTIVE / DELETE / ARCHIVE
- Should be stored against a relevant ID (tbc)
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
DELETE
ARCHIVE
...
INACTIVE
DELETE
...