...
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 | |||||
Actors | Local office admin | |||||
Pre-conditions | Logged in Authorised User | |||||
Post-conditions | Searched for person in entire database | |||||
Process steps |
| Rules | From People - Field Validation (when creating a person record only the fields in Personal and Contact and (for a trainee) Programme are required) Which fields are required in spreadsheet? People - Field Validation has a spreadsheet (bottom of page) that shows the fields How should upload errors be handled? Validation takes place prior to upload - message to appear to inform the user of the error so they can fix them before attempting the upload again | Alternative flow | PP5- Create person (single) | Error: this GMC/GDC/Public Health number is already held 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 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. |
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 | |||||
JIRA Reference | TIS-642 | |||||
Audit Log | Who created the people record and when | Log changes to any of the field values and when and who made the changes. Visually presented to all |
...
Process Name | PP7 - Manage Oriel Import of Trainees | Comments |
---|---|---|
Description | Users should be able to view a summary of recently imported trainee person records and edit the contents of each one | |
Actors | Local office admin | |
Pre-conditions | Logged in Authorised User | |
Post-conditions | ||
Process steps | Mandatory fields should be defined on the import spreadsheet to avoid the non import of records.
How do you currently view/edit import errors? Joanne Watson (Unlicensed) 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 total number of records that have been imported is shown to the operator.
| How do you currently view/edit import errors? Joanne Watson (Unlicensed) Need to check this with colleagues who use the Oriel import |
Alternative flow | PP6-Bulk upload of People | |
Rules |
| Where mandatory fields are not complted at time of import suggest a quality dashboard/data extract be produced to indicate the missing values in each person record |
JIRA Reference | TIS-715 | |
Audit Log | Who created the people record and when | Log changes to any of the field values and when and who made the changes. Visually presented to all |
...