...
| Process Name | PP6 - Bulk Upload of People | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Description | A user should be able to add a list of individuals to create multiple person records in one go | Intrepid Excel Template is Intrepid Recruitment Import Template v11.xls For TIS, the only mandatory fields identified in the template are:
The only roles would be 'Doctor in training' and 'Trainee'. | ||||||||
| Actors | Local office admin | |||||||||
| Pre-conditions | Logged in Authorised User | |||||||||
| Post-conditions | Searched for person in entire database | |||||||||
| Process steps |
| From People - Field Validation (when creating a person record only the fields in Personal and Contact and (for a trainee) Programme are required) Fields People - Field Validation has a spreadsheet (bottom of page) that shows the fields GMC/GDC/PH number is the Unique identifier for updating records exist on the system. Foundation trainees - If they do not have a GMC, a second source identifying the person would be the email address. | ||||||||
| Alternative flow | PP5 - Create person (single) | |||||||||
| Rules | Error: this GMC/GDC/Public Health number is already held by a person on this database Error: mandatory fields not completed Error: Structure of the template expected by the import does not match, i.e. file format/column names/order expected do not match Error: Duplicate rows identified in the spreadsheet Error: Duplicate record of a person that already exist on the system to be validated against | Error message appears to let the operator know what the reasons for non import are. The errors should be corrected on the import spreadsheet before the import function is tried again. It is possible to select records to be imported if some of the records are correct but the best course of action is to correct all inaccuracies and import the entire spreadsheet in one go. The error messages should list the the rows and columns for failures. The total number of records that have been imported is shown to the operator. Mandatory fields should be defined on the import spreadsheet to avoid the non import of records. | ||||||||
| JIRA Reference | TIS-642
| |||||||||
| Audit Log | Who created the people record/s and when Who updated the prople record/s and when | Log changes to any of the field values and when and who made the changes. Visually presented to all |
| Process Name | PP6A - Bulk Update People using TIS_Person_ID | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Description | A user should be able to:
| |||||||||
| Actors | (HEE Admin, HEE Admin Sensitive, HEE Admin Reval, HEE TIS Admin) | |||||||||
| Pre-conditions | Logged in Authorised User | |||||||||
| Post-conditions |
| |||||||||
| Process steps |
| People - Bulk Update (DRAFT)Uploads | ||||||||
| Alternative flow | PP4 - View/Edit person (single) | |||||||||
| Rules | People - Bulk Update (DRAFT)Uploads Error: TIS_Person_ID does not exist on TIS Error: mandatory fields not completed Error: Structure of the template expected by the import does not match, i.e. file format/column names/order expected do not match Error: Duplicate rows identified in the spreadsheet | Error message appears to let the user know what the reasons for non import are. The errors should be corrected on the import spreadsheet before the import function is tried again. It is possible to select records to be imported if some of the records are correct but the best course of action is to correct all inaccuracies and import the entire spreadsheet in one go. The error messages should list the the rows and columns for failures. The total number of records that have been imported is shown to the operator. Mandatory fields should be defined on the import spreadsheet to avoid the non import of records. | ||||||||
| JIRA Reference |
| |||||||||
| Audit Log | Who updated the people record/s, what was updated from what to what and when | Log changes to any of the field values and when and who made the changes. Visually presented to all |
...