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.
In conclusion, deletion could continue to be applied by status, however each status would imply a particular action. These are described below:
Inactive
- the field/form can be viewed on TIS UI if it has been applied to a record. For example, reference values that have been made inactive in their respective table are rendered read only, or can be removed from a TIS form
- the inactive field cannot be viewed in the TIS UI drop downs. For example, reference values that have been made inactive in their respective table are no longer viewable within drop downs across TIS forms
- the inactive form cannot be linked to any other record. For example an inactive post cannot be linked to a trainee and become a placement
Delete
- 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
Note:
A "form" is the TIS UI format of a particular set of data in TIS e.g. Person screen = a form
A "record" can refer to either a table or a form within TIS, so is not used in this page to remove confusion
This will need to be updated once "missing" fields have been agreed for the TIS UI (see here: NDW UAT feedback)
Add Comment