[AQTS-979] Prioritisation - "Other work history in England" within application form #2781
Conversation
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
Hassanmir92
force-pushed
the
AQTS-979-dev-prioritisation-application-form
branch
2 times, most recently
from
eb908f1 to
f0da2cc
Compare
This will be used to determine whether the new "Other work experience in England" entries will be available to the applicant or not. It will be based on whether at the time of the application form being generated, the feature flag for "prioritisation" was enabled or not.
This commit introduces the flow where once the applicant has completed the "work history" entries, another task item is presented to them for "Add other work experience in England" where they will enter other work history entries with validations in place where it must be in England and a postcode must be present. Unlike the regular work history entry, we do not capture any hours worked in these roles as they will not be counted towards their work history months when assessing and purely for the purpose of prioritisation. This commit introduces a new column within the work_histories table "is_other_england_work_history_role" which creates a separation between regular teaching roles that will count towards work history and these new type of roles which are purely for prioritisation purposes.
…hs" form to ensure end date of an experience cannot be over 12 months ago if they are not still employed in the role
…ies for work history duration calculation The WorkHistoryDuration was already excluding it as hours_per_week is not present on other work history roles but as an extra step, we are adding the teaching_role scope as well
…answers before submitting your application" page for applicants that have provided it
… work experience in England" spoke if they have not yet started it This allows a natural flow into the "Other work experience in England" if it is their first time without taking the user to the main application task list. Updates to the normal work history spoke after completing both of these steps will no longer link the two and instead takes the user to the application task list instead.
…on assessment and verification stages for reference requests
Hassanmir92
force-pushed
the
AQTS-979-dev-prioritisation-application-form
branch
from
1d93c5c to
7303dc8
Compare
Hassanmir92
changed the title
|
Review app deployed to https://apply-for-qts-review-2781-web.test.teacherservices.cloud/personas |
|
Review app for PR 2781 was deleted |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Tickets:
https://dfedigital.atlassian.net/browse/AQTS-979
https://dfedigital.atlassian.net/browse/AQTS-980
This work introduces the new "Other work experience in England" spoke within the application form. This new task item for application forms becomes available once the applicant completes their "work history" task. The purpose of this new task item is to capture any work experience that the applicant may have in England which may not necessarily be a teaching role but is within an educational setting.
Following the completion of "work history" applicants are presented with a question around whether they have other educational work experience in England within the last 12 months.
Only when applicants select "Yes, I have other work experience in England that meets this criteria" they will then need to start filling out these records which is almost identical to the normal work history with key content difference, with not "Hours worked per week", validation to ensure the country must always be "England" and validation in place on the "End date" that either the applicant is either still employed or the end date is within the last 12 months. Beyond this step, the referee details form will be identical to the normal work history.
The flow also ends up asking the applicant whether they want to add more valid educational work experience in England which is similar to the normal work history task.
These new roles do not qualify towards the number of years/months of teaching experience the applicant needs to have to qualify for QTS and act purely as information used to determine whether they are prioritised.
The new "Other work experience in England" are also stored as
work_historiesrecords with a key difference of having a new columnis_other_england_educational_roleastrueand they do not havehours_per_weekset as there is no need for determining the duration of months worked in these roles and only whether they were in the last 12 months. Additionally, using this key difference, existing functionality has been added to exclude all these new type of work history records from work history month calculations and what is displayed to to assessors during assessment and reference checks.Notes:
This new flow is not included on existing applications and only available on applications which have
includes_prioritisation_featuresset astruewhich is only when theprioritisationfeature flag is active. This design ensures that we can ship this feature hidden behind a feature flag.