Programmes - Schools Field Validation & Scenarios ||| PLACEHOLDER - NONE OF THE CONTENT ON THIS PAGE IS RELEVANT TO SCHOOLS|||

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.

Scope for TIS

Act as Reference Data
Available as labels / drop downs within relevant components in the Admin UI
Editable by the local office and data leads
Functionality should include -
- create rotation
- view/edit rotation
- remove rotation
- assign rotation

Currently

users can associate rotations with programmes or with posts
so a trainee can be assigned to two different rotations depending on who set it up
trainee never sees the rotation, so no impact to them
however the database will hold two sets of records and any component sing the rotations will need to know which to pick up

These two tables can be consolidated into a single table, then mapped to existing data in TIS:

Field Validation

Field Sequence

Field name (V10)

DR field

Reference table

Example value

Other fields available in DR

Type (free text, drop down, check box) & Interaction

Mandatory (Y/N)

Validation / Error Messaging

Filter (Y/N)

Search (Y/N)

Sort (Y/N)

Summary (S) / Detail (D)

Notes

Delete (Y / N)

1

Rotation Name

Free text

Y

Must be unique per local office

2

Programme Name

Smartsearch drop down

Y

Must select 1

3

Programme Number

Derived from programme name

Y

Must select 1

4

Rotation Status

Drop down

Y

Must select 1

5

Start Date

Calender picker

Y

Must select 1

6

End Date

Calender picker

Y

Must select 1

Scenarios

Process Name	PG-1 Create Rotation	Comment
Description	User creates the Rotation grouping so that this can be used elsewhere in TIS
Actors	HEE Admin
Pre-Conditions	Programmes must be defined User must have appropriate access
Post Conditions	Rotation group created and available to be assigned to People
Process Steps	Navigate to reference data space Select to create new Enter all mandatory fields Rotation name Programme name Programme number (autopopulated) Status Start Date End Date Save New rotation grouping is available across TIS
Alternative Flow	N/A
Rules	name is free text limit to 25 characters
JIRA Reference	TISDEV-3102 - Getting issue details... STATUS
Audit Log	Create record - who / when

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	TISDEV-3103 - Getting issue details... STATUS
Audit Log	Edit record - who/when

Process Name	PG-3 Remove Rotation	Comments
Description	User should be able to remove a Rotation grouping
Actors	Programme / Placement Admin
Pre-Conditions	Programmes must be defined User must have appropriate access
Post-Conditions	Rotation removed from Reference Table Rotation field shows as blank in other records
Process Steps	Navigate to reference data space Select field to be edited Change status to inactive Save
Alternative Flow	N/A
Rules	Downstream data remains as is i.e. Trainee-Placement link remains in place Display warning message displayed to warn user of potential impact to previously/already linked Programmes, Trainees, Posts etc Remove display of Rotation label within records where applicable
JIRA Reference	TISDEV-3104 - Getting issue details... STATUS
Audit Log	Delete record

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	Only one rotation 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	TISDEV-3336 - Getting issue details... STATUS
Audit Log	add rotation - who when edit rotation - who/when

For Discussion

#	Question	Comment	Owner
1	in TIS, is it actually necessary to assign rotations at both post and programme levels? Alternative would be to expose rotation grouping to all admins and set a rotation group max number so they remain manageable for all users?	No, not necessary under new process - link rotation to programme, then assign rotation to person and/or post	Alistair Pringle (Unlicensed)
2	what other components use rotations?	none	Alistair Pringle (Unlicensed)
3	Is it possible to combine the 2 old rotations tables into one, as well as any new rotations labels created? potential impacts - localised v national views, duplicate labels	yes, see ppt above	Russell Steel (Unlicensed), Alistair Pringle (Unlicensed), Alex Dobre (Unlicensed)
4	how should legacy rotations be displayed in TIS?	As single value against a record	Alistair Pringle (Unlicensed)