...
...
...
...
...
...
...
...
Background
Rotations are groupings used to manage large groups of trainees on a single Programme; they are artificial and do not represent any form of reportable data within HEE by themselves.
...
| Process Name | PG-2 View / Edit Rotation | Comment |
|---|
| Description | User should be able to view and make edits to existing Rotation groupings |
|
| Actors | HEE Admin TIS Admin |
|
| Pre-Conditinos | Programmes must be defined User must have appropriate access |
|
| Post Conditions | Changes saved to already created Rotation |
|
| Process Steps | - Navigate to reference data space
- Select field to be edited
- Make changes
- Save
|
|
| Alternative Flow | N/A |
|
| Rules | - Changes can be made to name or programme link
- Display warning message displayed to warn user of potential impact to previously/already linked Programmes, Trainees, Posts etc
|
|
| JIRA Reference | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
|---|
| key | TISDEV-3103 |
|---|
|
|
|
| Audit Log | |
|
...
| Process Name | PG-4 Assign Rotation | Comments |
|---|
| Description | User can link a rotation grouping to TIS data, such as trainee or post |
|
| Actors | HEE Admin |
|
| Pre-Conditions | Record does not contain a link to desired rotation |
|
| Post-Conditions | Record contains a link to desired rotation |
|
| Process Steps | - Navigate to record
- Select rotation from drop down
- Save record
- Display rotation grouping against record
|
|
| Alternative Flow | N/A |
|
| Rules | - Multiple rotations can be selected per record
- Historical view diplayed via audit log only
- Display warning message where rotation field is edited and is linked to another record i.e. Person is in Placement and one of the fields is changed
- Only Current rotations can be selected
|
|
| JIRA Reference | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
|---|
| key | TISDEV-3336 |
|---|
|
|
|
| Audit Log | - add rotation - who when
- edit rotation - who/when
|
|
| Process Name | PG-5 Bulk Add/Update Rotation 1 to Trainees | Comments |
|---|
| Description | *As a* Local Office Admin
*I want* to be able to link multiple People records to a Rotation efficiently via a spreadsheet upload
*So that* I don't have to manually choose a Rotation for each Trainee individually through the Person record in the UIr can link a rotation grouping to TIS data, such as trainee or post |
|
| Actors | HEE Admin |
|
| Pre-Conditions | Logged in
Authorised User |
|
| Post-Conditions | - New Person records created on TIS
- Where Person records already exist and the Programme matching criteria met, the records get Added/Updated with the Rotation 1 value from the spreadsheet.
- Person record contains a link to desired rotation
|
|
| Process Steps | - Download the TIS People Import template
- Populate the spreadsheet with people records and Rotations
- Upload spreadsheet
- System validates spreadsheet and presents validation errors if any
- System creates/update new records based on spreadsheet values
- System presents confirmation when process completes
| TIS People Import Template with Add/Update specified: TIS Recruitment Import Template - with Add anf Update fields.xlsx TIS People Import Template (to be made downloadable from the FE): TIS People Import Template.xlsx
|
| Alternative Flow | PG-4 Assign Rotation |
|
| Rules | - This is a non-mandatory field.
- It is an 'Update' type field
- Although on the Front End we can add multiple Rotations to the ProgrammeMembership of a Person record, from the Bulk Import we should only allow one to be added initially or updated with subsequently.
I.e. If you are creating a new person record with a prog membership and specify a rotation then you want it added. Re multiple rotations - this is very rare and shouldn't be done via the import, only manually in the system. Therefore if you update a record and specify a different rotation with matching prog membership then you would want it to replace the value rather than add to it. - Accepted values for Rotation 1 on the template are only one of those attached to the Programme specified and are Current, else should present an error. I.e. Can only add to a Rotation linked to the programme membership you are adding.
- You should not be allowed to specify a Rotation without entering 'Programme name' and 'Programme number' details on the template. This should present an error.
- If a blank value specified, no action by the import.
|
|
| JIRA Reference | TISDEV-4216 |
|
| Audit Log | - Who created the people record and when
- add rotation - who when
- edit rotation - who/when
|
|
...