This page is shows where we are with PPT (what we have done so far) and what still need to be done in terms of users feedback
...
Can move ‘Approved’ placement to ‘Draft’ and then re-approve (if there is need for that to make changes). BUT any changes made to this placement will not go to ESR except if it is placement start from and to date to change ( for change of date, it will follow the normal change of date notification agreed with ESR and send date changes notification to ESR ). Moving ‘Approved' placement to ‘draft’ won’t withdraw any notification from ESR. User will need to use ‘Delete’ button to withdraw a placement which is the BAU (it has not changed) and ESR will get a withdrawal Notification.
Can use the ‘Update’ button to update placement fields in ‘approved’ state without need to move to draft. BUT any changes made to this placement will not go to ESR except if it is placement start from and to dates change ( for change of date, it will follow the normal change of date notification agreed with ESR and send date changes notification to ESR )
...
Placements in ‘draft’ are display in the UI with a red ring round the placements to differentiate from ‘approved’ placements. ‘Approved’ placement will not any coloured ring round it
Past Placement appears grey?
Present Placement appears Green?
Future Placement appears Amber?
Placement types:
What still need to be done/prioritise
...
Placement Bulk Upload permission for Programme and Trust admin roles: 2 options to be decided by Dev team/PO; either; a) Ideally restrict them (Programme and Trust admin roles) from being able to bulk upload placements OR b) Set to DRAFT only for these 2 types of users when bulk uploadingplacements . https://hee-tis.atlassian.net/browse/TISNEW-3657
Amendments/Update made to CURRENT/PAST placements, the status to remains in APPROVED for Programme Admin User Only. https://hee-tis.atlassian.net/browse/TISNEW-36573656
TISNEW-3656 Amendments/Update made to CURRENT/PAST placements, the status to remains in APPROVED
...
SCENARIO: Amendment/Update of dates to Past, Current and Future placements that are in approved state
We want to know what happens to the combinations if the amended dates fall into the past, current and future for Programme Admin users:
Placement/update fields | Past | Current | Future |
Past | Approved | Approved | Draft |
Current | Approved | Approved | Draft |
Future | Stop from happening- Just delete- Create a ticket: https://hee-tis.atlassian.net/browse/TISNEW-3852 | Stop from happening- Just delete and create a new one- Create a ticket; https://hee-tis.atlassian.net/browse/TISNEW-3852 | Draft |
PPT Users Permissions:
Mugabee: Need to find out the difference between TPD and Admin users?
Response: You don’t need to know the concept but if interested James can talk you through
Mugabee: Our thought for this ticket is that it is Just TPD user
Response: It is only for programme Admin users
Bulk Upload Permission: Any user that can create placement and update/edit placements on UI should be able to Bulk upload. This permission will be withdrawn for Progamme Admin and Trust Admin roles.
Type of users | Bulk upload (placement stays as approved and not draft in Bulk Upload) | Create Placement in UI
Placement stays as Draft/approved? | Approve Placement in UI | Update/Amend Placement in UI
Placement stays as Draft/approved? | Comment |
HEE Trust Admin | No | Yes | No | Yes | |
HEE Admin | Yes | Yes | Yes | Yes |
|
HEE Admin Sensitive | Yes | Yes | Yes | Yes |
|
HEE Admin Revalidation | Yes | Yes | Yes | Yes |
|
HEE TIS Admin | Yes | Yes | Yes | Yes |
|
HEE Programme Admin | No | Yes | No | Yes |
...
TcsAdmin | Yes | Yes | No | Yes |
|
BulkUploadAdmin | Yes | Yes | Yes | Yes |
|
PersonAdmin | Yes | Yes | No | Yes |
|
ETL | Yes | Yes | No | Yes |
|
Other tickets raised
Feedback from PPT demo: Need to be prioritised and tickets raised where necessary
...