Sprint 6 Review (2019-11-13 to 2019-11-26)

ESR

Write generated App records to file and upload

AWS Lambda - allows new system to be eventful

Generation of APP files

Upload of APP files to AWS

Update File Splitter Service to work with AWS

Where we were as of the Sprint 5

Where we are now at the end of Sprint 6

Demo

https://www.loom.com/share/8fee77cffe144b6dadece6b18de60980

Training Pathway - automatically set by default based on curriculum selection on Programme membership.

TISNEW-3389 - Getting issue details... STATUS

• If Curriculum leads To CCT, then default Training Pathway to CCT
• If Curriculum does not lead to CCT, then default Training Pathway to N/A
• If at least one of the curricula attached Leads to CCT (where there are multiple), then default Training Pathway to CCT when creating/updating programme membership
• Exception: If Training Pathway was set to CESR: Keep as CESR when adding/changing curricula, but this can be manually overridden
• In any of the cases, you are able to override the default value on update/create journeys.
• If a user updates the LeadsToCCT value in the curriculum reference, then no action retroactively on existing prog. memberships.

TISNEW-3492 Create/see/review the placement plan in draft before publishing

• Added 'Approve All' button to PPT for approving all placements in the programme
• Added the 'Approval' field in the placement create/ update page

NOTE: Draft placements will have a red border in the PPT.

Approved users (e.g. HEE Admin)

1. Add 'approve all placements button' and confirmation modal popup for approved users
2. Display drop-down menu (with options: APPROVED, DRAFT) for DRAFT placements
3. Disable the Approval field for APPROVED placements but allow other fields to be updated
4. The new placements created with the bulk-upload function will be set as 'Approved' by default

Unapproved users

1. Lock Approval field for non-approved users but allow them to update other fields on DRAFT placement.
2. Remove the 'update' button for non-approved users for placements that have been APPROVED

We identified a set of libraries that we'll use for building the user interface, either, straight-away or very soon after starting.

As part of the conversation it was clear that we would end up needing to spend some time evaluating how well these libraries fit what we are developing, including changes to our understanding of what Doctors in Training want to see.

The "Leaving Destination" field has been replaced with a new "Leaving Reason" field with the following values available:

 - Completed training

 - Removed from training programme

 - Inter deanery transfer

 - Left without CCT - employment not known

Some work remaining to send the new column to NDW.