Placements - Scenarios
Process Name | PL1 - Navigate to Placements | Comments |
Description | User can access placement management tools | |
Actors | HEE Admins | |
Pre-conditions | Logged in Security allows access to placement manager | |
Post-conditions | View options to create / edit placements | |
Process steps | 1. Hover over Placements in nav bar 2. Select either Create Placement, Bulk Upload or Placement Manager 3. System presents appropriate screens as requested | |
Alternative flow | N/A | |
Rules | Page only available to those who have access to 'Placements' in their role | |
JIRA Reference | ||
Audit Log | N/A |
Process Name | PL2 - Search | Comments |
---|---|---|
Description | User should be able to find placement details by searching for a person or post number | |
Actors | HEE Admin | |
Pre-Conditions | Logged in Security allows access to Posts, People or Placement Manager | |
Post-Conditions | User is able to find specified data around a Placement User is told there are no details related to their particular search | |
Process Steps |
| |
Alternative Flow | N/A | |
Rules | Usual smart search rules apply | |
JIRA Reference | ||
Audit Log |
Process Name | PL3 - Create Placement from Person Record | Comments |
---|---|---|
Description | User can create placement related to an individual person | |
Actors | HEE Admins | |
Pre-Conditions | Logged in Security allows access to Posts, People or Placement Manager Person search completed | |
Post-Conditions | Placement created for a single individual Placement confirmed to relevant Trust | |
Process Steps |
| Post Details to be pre-populated
|
Alternative Flow | PL4 - Create Bulk Placements PL6 - Manage Multiple Placements | |
Rules | WTE default is 1 WTE - warn user that if the role is a slot share, they should add 10% MIP default 0 on create | |
JIRA Reference | TISDEV-2726 | |
Audit Log |
Process Name | PL4 - Create/Update Bulk Placements | Comments |
Description | User can create or Update placement related to a group of people. In simple terms, it is the building or updatng of the relationships between Posts and People. | |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to Placement Manager Trainees to exist on TIS already Posts to exist on TIS already | |
Post-conditions | Placement created for a group of individuals Placement confirmed to relevant Trust | |
Process steps |
| Please see Placement Import Template with specification of
With Comments: TIS Placement Import Template - Add-Update-Matching Criteria.xls Blank Upload Template to be made available for download on TIS: Without Comments TIS Placement Import Template.xls |
Alternative flow | PL10 - Upload Errors | |
Rules | Valid template with exact column headers downloaded from TIS to be used. Structural errors to be validated for. All fields must be completed with a valid response. Rules and Validations for each column are specified in the 'Rules and Validations' sheet here: TIS Placement Import Template - Spec for Update v.s. Add fields.xls | |
JIRA Reference | - TISDEV-3119Getting issue details... STATUS | |
Audit Log | Who uploaded the template and when. Who added/updated a placement and when. |
Process Name | PL4B - Bulk Update Placements using TIS_Placement_ID | Comments |
Description | As a Local Office Admin I want to Bulk update Placements using TIS_Placement_IDs as the only matching criteria So that I can update any/all other fields on the Template. | |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to Placement Manager Trainees to exist on TIS already Posts to exist on TIS already Placements to exists with the Specified TIS_Placement_ID/s | |
Post-conditions | Placement updated for a group of trainees | |
Process steps |
| Please see column specification for 'TIS Placement Update Template' with:
Placements - Field Validation#FieldValidation-Placements-BulkUpdateusingTIS_Placement_IDs Blank Upload Template to be made available for download on TIS: |
Alternative flow | PL4, PL10 | |
Rules | Valid template with exact column headers downloaded from TIS to be used. Structural errors to be validated for. All fields must be completed with a valid response. Rules and Validations for each column are specified here: Placements - Field Validation#FieldValidation-Placements-BulkUpdateusingTIS_Placement_IDs | |
JIRA Reference | - TISDEV-4441Getting issue details... STATUS | |
Audit Log | Who uploaded the template and when. Who added/updated a placement and when. |
Process Name | PL5 - View/Edit Placement | Comments |
---|---|---|
Description | User can view and edit current/future placement data already created | |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to People, Posts, Placement Manager | |
Post-conditions | User views placement detail (past / current / future) User edits placement detail (current / future) | |
Process steps |
| Editable fields include:
|
Alternative flow | PL8 - Manage Placements with Slot Share | |
Rules | System prevents user from editing past placement detail | |
JIRA Reference | TISDEV-2727 | |
Audit Log |
Process Name | PL6 - Manage Multiple Placements | Comments |
---|---|---|
Description | User can link / unlink posts for multiple trainees to create multiple placements in one view | Not MVP |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to Placement Manager | |
Post-conditions | Placement created for a group of individuals Placement confirmed to relevant Trust | |
Process steps |
| Rotations can be created in Programme TBC?? Posts detail in view
Person detail in view
|
Alternative flow | ||
Rules | Trainees and Posts avaiable should be constrained to the local view only Filter out "trainees in post" | |
JIRA Reference | ||
Audit Log |
Process Name | PL7 - Unlink Placement | Comments |
---|---|---|
Description | User is able to remove Person from a Placement with immediate effect | |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to People, Posts, Placement Manager | |
Post-conditions | User is removed from Placement | |
Process steps |
| |
Alternative flow | PL9 - Placement Ends | |
Rules | tbc | |
JIRA Reference | ||
Audit Log |
Process Name | PL8 - Manage Placements with Slot Share | Comments |
---|---|---|
Description | User can view and edit current/future placement data already created; specifially related to Slot Share details | |
Actors | HEE Admin | |
Pre-conditions | Logged in Security allows access to People, Posts, Placement Manager | |
Post-conditions | User edits slot share information in placement detail (current / future) | |
Process steps |
| |
Alternative flow | N/A | |
Rules | Slot share must always be 0.5 + 0.1 for both trainees sharing a single slot (to account for handover time) System prevents user from editing past placement detail | WTE should allow anything between 0 and 1. ticket needs updating. |
JIRA Reference | TISDEV-2727 | |
Audit Log |
Process Name | PL9 - Placement End | Comments |
---|---|---|
Description | Automatic unlinking of Post from Person where the Placement end date has passed | |
Actors | TIS | |
Pre-conditions | Placement is active | |
Post-conditions | Placement is inactive | |
Process steps |
| |
Alternative flow | PL-7 | |
Rules | TBC | |
JIRA Reference | TISDEV-2727 | |
Audit Log |
Process Name | PL10 - Upload Error | Comments |
---|---|---|
Description | User can view errors by line as part of the bulk upload journey | |
Actors | HEE Admin | |
Pre-Conditions | Logged in Security allows access to Placement Manager Initial spreadsheet upload has been completed | |
Post-Conditions | Upload errors displayed by Spreadsheet Line | |
Process Steps |
| |
Alternative Flow | PL4 - Create Bulk Placements | |
Rules | Rules and Validations for each column are specified in the 'Rules and Validations' sheet here: TIS Placement Import Template - Spec for Update v.s. Add fields.xls | |
JIRA Reference | ||
Audit Log |
Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213