Versions Compared

Old Version 40

changes.mady.by.user Ashley Ransoo

Saved on

compared with

New Version Current

changes.mady.by.user Reuben Noot (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Content

Table of Contents
Background

...

The next increment of data design and UI ideas can be found in here: TIS Rotations ERD V1.12.pptx


TIS Rotation ERDImage RemovedImage Added

An initial refactor of the design for the UI interactions is outlined here: TIS Rotations UI design ideas V1.0.pptx

...

Process NamePG-2 View / Edit RotationComment
DescriptionUser 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 ConditionsChanges saved to already created Rotation
Process Steps
  1. Navigate to reference data space
  2. Select field to be edited
  3. Make changes
  4. Save

Alternative FlowN/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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-3103


Audit Log
  • Edit record - who/when

...

Process NamePG-4 Assign RotationComments
DescriptionUser can link a rotation grouping to TIS data, such as trainee or post
ActorsHEE Admin
Pre-ConditionsRecord does not contain a link to desired rotation
Post-ConditionsRecord contains a link to desired rotation
Process Steps
  1. Navigate to record
  2. Select rotation from drop down
  3. Save record
  4. Display rotation grouping against record

Alternative FlowN/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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-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
ActorsHEE Admin
Pre-ConditionsLogged 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
  1. Download the TIS People Import template
  2. Populate the spreadsheet with people records and Rotations
  3. Upload spreadsheet
  4. System validates spreadsheet and presents validation errors if any
  5. System creates/update new records based on spreadsheet values
  6. System presents confirmation when process completes

TIS People Import Template with Add/Update specified:

View file
nameTIS Recruitment Import Template - with Add and Update fields.xlsx
height150

TIS People Import Template (to be made downloadable from the FE):

View file
nameTIS People Import Template.xlsx
height150



Alternative FlowPG-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
    • Only 1 Rotation can be added/edited per ProgrammeMembership of a Person record from the FE, from the Bulk Import we
    • should only allow one to be added initially or updated with subsequently.
    • expect a similar behaviour
      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
    •  
      If you are updating a record and specify a different rotation with matching
    • prog
    • person and programme membership then you would want it to replace the value
    • rather than add to it
    • held.
    • 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 import 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 ReferenceTISDEV-4216
Audit Log
  • Who created the people record and when
  • add rotation - who when
  • edit rotation - who/when

...