Finalise data relationship between CPD and TRS consoles

[kas-madrigal]

Why?

Define admin console rules for CPD, and a set of rules which dictate when updates should / shouldn't be possible in CPD or TRS console (including exemption rules).

Helpful links or other information

https://educationgovuk-my.sharepoint.com/:x:/r/personal/kas_madrigal_education_gov_uk/Documents/Admin%20console%20data%20considerations.xlsx?d=w0bf2a240d8334f328a8013bd88cc81db&csf=1&web=1&e=mfBiq1

https://educationgovuk.sharepoint.com/:x:/r/sites/TRATransformationTeamDocs/Shared%20Documents/General/TRS%20Products/Induction%20Data%20Migration/Induction%20events.xlsx?d=w027ec7affa99439d8c23ab05b87b19a3&csf=1&web=1&e=46JMGj

[joe-harrison-dfe]

Notes from Emily P:

• None - editable by TRS & CPD
• Required to complete - Editable by TRS & CPD

Both editable by both TRS & CPD but only editable by TRS in the following scenarios:

• Updating induction status to Exempt

• Updating historic inductions

• Exempt - editable only by TRS

• In progress - editable by both TRS & CPD

For in progress, we can define a rule around 'allowed' status transitions here. Think the only valid status update via TRS here is In Progress -> Exempt. We're planning on creating records for all "in flight" inductions in CPD. So if someone approached us with evidence they'd passed their induction, but they hadn't, we'd need to make sure this was only done via CPD, so we could close their record down.

• Passed - editable by both TRS & CPD but time bound?
• Fail - editable by both TRS & CPD but time bound?

There are a couple of scenarios where updating a Pass/Fail status might require an induction to continue:

• AB mistakenly recorded an outcome and wants to hit the "undo" button - we'd need to update the induction in CPD in order for the induction to continue and the actual outcome to be recorded at the right time.
• An ECT lodges a complaint against a Fail outcome, and there is a decision to overturn and award an extension instead. We'd need to update the induction in CPD with the extension, and allow an outcome to be recorded at the end of the extension. Should be a rare event though!

Both of the above should happen quite soon after an outcome is recorded (Think appeals need to be lodged within 30 days of the outcome, but the appeal outcome may take a little longer) so it feels like we could set some sensible time restrictions, where anything outside of this must be handled manually.

• Passed in Wales - editable only by TRS
• Failed in Wales - editable only by TRS

[peteryates]

When we say "editable by both TRS and CPD", given that we will only be storing each value once so there's no room for confusion over source of truth, I assume that means we'll just send changes directly to TRS via the API without recording anything in the CPD database?

Any form of two way sync will be painful.