CAPT 3133/ey practitioner journey prototype#4306
Draft
Conversation
rjlynch
force-pushed
the
CAPT-3133/ey-practitioner-journey-prototype
branch
from
cc79888 to
1e10d9e
Compare
rjlynch
force-pushed
the
CAPT-3133/ey-practitioner-journey-prototype
branch
from
1e10d9e to
b76de8c
Compare
rjlynch
force-pushed
the
CAPT-3133/ey-practitioner-journey-prototype
branch
from
edbe1ea to
8978423
Compare
rjlynch
force-pushed
the
CAPT-3133/ey-practitioner-journey-prototype
branch
2 times, most recently
from
3c89ae6 to
81358a1
Compare
Now we're supporting prototypes in the Rails application we need to be able to set the phase banner.
As this is a prototype we've intentionally left out tests as we'll need to be flexible with the design. This journey follows the existing journey mechanic with some trickiness to handle the looping add teacher forms. The `ProviderTeacherDetailsForm` handles creating, updating, and deleting teachers depending on whether a `teacher_id`, or `remove_teacher` parameter is passed to the form. We reuse the navigator's `change` slug functionality to send the user back to the right place. `teacher_details_form_completed` is set to determine if this form needs to be rendered. On the `ManageTeachersForm`, if the provider wants to add another teacher we set `teacher_details_form_completed` to false, causing the navigator to send the user to the `ProviderTeacherDetailsForm`. There may be a neater way to do this but this works with the existing journey navigation code and works well enough for a prototype.
As this is a prototype we've intentionally left out tests as we'll need
to be flexible with the design.
This journey follows on from the practitioner journey, and will start from
an email link sent to claimants who we already know work at eligible
establishments.
We're prompting the user to sign in with TID for two reasons
1.) The email we send them asks them to check their qualifications,
which requires they sign in with TID, so hopefully most teachers will
have created an account before hitting our service.
2.) Part of the goal for the service is to help the DfE contact early
years teachers, so we would like them to setup a TID account.
As per the other journeys we offer the option to skip teacher id and
provide the details we need manually.
I imagine we'll validate their qualification and employment after the
check answers (or confirm details if logged in with tid) screen with an
api call to HMRC & TRS, and if ineligible that will be the point to show
them the ineligible screen. Not sure what the govuk pattern is for
a loading page is, but we'll probably need one if we're waiting on two
api calls, don't need to worry about that for the prototype.
We'll also likely need to add in a "how we'll use your information"
page, though that wasn't in the designs.
Removes the decelartion and replaces it with new copy
We don't want to confuse participants with hmrc validation errors, and we don't want them to have to put in their real bank details or national insurance numbers.
Removes redundent screens. Add OL
Just adding this as a quick work around when using this review app for user testing. Will drop this commit before merging to master.
For each teacher we need to have a sub wizard to show the performance and discipline journey. To get this working with the navigator and the various subwizard stats (ineligible) we've had to do some serious hacks (backlinks acting as forms etc). Thankfully this journey is just for prototyping and will be deleted when alpha is done!
rjlynch
force-pushed
the
CAPT-3133/ey-practitioner-journey-prototype
branch
from
f840933 to
64ee8b1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ADD initial eytfi practioner prototype
As this is a prototype we've intentionally left out tests as we'll need
to be flexible with the design.
This journey follows on from the practitioner journey, and will start from
an email link sent to claimants who we already know work at eligible
establishments.
We're prompting the user to sign in with TID for two reasons
1.) The email we send them asks them to check their qualifications,
which requires they sign in with TID, so hopefully most teachers will
have created an account before hitting our service.
2.) Part of the goal for the service is to help the DfE contact early
years teachers, so we would like them to setup a TID account.
As per the other journeys we offer the option to skip teacher id and
provide the details we need manually.
I imagine we'll validate their qualification and employment after the
check answers (or confirm details if logged in with tid) screen with an
api call to HMRC & TRS, and if ineligible that will be the point to show
them the ineligible screen. Not sure what the govuk pattern is for
a loading page is, but we'll probably need one if we're waiting on two
api calls, don't need to worry about that for the prototype.
We'll also likely need to add in a "how we'll use your information"
page, though that wasn't in the designs.
Drop these commits before merging