Subclass 482 — Application context (example)

Starts the visa application and links it to a related nomination. Read-only reference example — no values or nomination references.

Read-only reference example

This map mirrors docs/governance/SUBCLASS-482-FIRST-TWO-SCREEN-MAPS.md and uses only fictional field labels and option text. Use “Start a new version from this one” on the Approval tab to copy it into an editable draft.

Fields on this screen

Each field records its visible label, control type, SCA Connect data link, and any show/hide rule.

Current locationdropdownrequired
key: current_location · SCA field: applicant.current_location_country
Options: AUSTRALIA, Overseas — example country A, Overseas — example country B
Corrected (3 Sep 2026): this field is the applicant's current country/location, not an onshore/offshore status. The previous fictional test value "Onshore in Australia" was not one of the live control's visible options and was correctly rejected by exact-option matching; it has been replaced with the exact live option text "AUSTRALIA".
Has the applicant commenced or completed a skills assessment?yes-norequired
key: skills_assessment_held · SCA field: nomination.skills_assessment_held
Options: Yes, No
Live Edge testing (4th pass, confirmed) verified this question IS visible on the genuine initial Application Context screen, but ImmiAccount renders it as a visible prompt immediately followed by separate Yes and No radio buttons — NOT a conventional associated <label for> control like the two dropdowns on this screen. The label-only reader could not see it, so the page was reported as missing this question even though it was on screen (3rd-pass symptom). Marked promptRadioGroup so the exported pack adds the associated-radio-group-prompt match strategy, which only associates this field when a nearby group offers exactly the Yes/No options above. It stays a stable, always-visible signature field. Answering No still reveals the exemption questions below.
The applicant declares that they are not required to undertake a mandatory skills assessment.yes-noshown when skills_assessment_held = “No”
key: mandatory_skills_declaration · SCA field: nomination.skills_assessment_exemption_declared
Options: Yes, No
Corrected (9 Sep 2026): live evidence confirmed this declaration is revealed once the skills-assessment question is answered "No", and — like that question — it is rendered as a visible prompt immediately followed by its own separate Yes/No radio buttons, not a conventional associated <label for> control. The previous fictional label "Mandatory skills-assessment declaration" and label-only match strategy could never find the real control (whose visible prompt text is "The applicant declares that they are not required to undertake a mandatory skills assessment."), so once its trigger's answer became readable the field would still be reported as missing. Marked promptRadioGroup so the exported pack uses the associated-radio-group-prompt match strategy instead.
Reason skills assessment is not requireddropdownshown when skills_assessment_held = “No”
key: skills_assessment_exemption_reason · SCA field: nomination.skills_assessment_exemption_reason
Options: Occupation not on the relevant list (example), Assessing authority ceased operating (example), Other approved exemption (example)
Corrected (9 Sep 2026): live evidence confirmed the real on-page label is "Reason skills assessment is not required" — the previous label carried an extra word ("Reason a skills assessment is not required") that matched no real <label>, so once its trigger correctly revealed the dropdown it still reported as "could not be found on this page". Options are illustrative placeholders only; the real exemption list is not stored in this workspace.
Reference number typedropdownrequired
key: reference_number_type · SCA field: matter.linked_nomination_reference_type
Options: Application ID, Nomination Application Transaction Reference Number (TRN)
Reference numbertextshown when reference_number_type = “Application ID”
key: linked_application_id · SCA field: matter.linked_application_id
Corrected (17 Sep 2026): the box revealed by this branch is the SAME physical control revealed by the TRN branch, labelled "Reference number" on the real page — not "Application ID" (that is only the choice in the "Reference number type" dropdown above it). The previous fictional label "Application ID" matched no real <label>, so once the trigger correctly revealed the box, this field's candidateCount was still 0 and it was reported "could not be found on this page". Mirror of the 9 Sep linked_trn correction. Example placeholder only — no real application identifiers are stored in this workspace.
Reference numbertextshown when reference_number_type = “Nomination Application Transaction Reference Number (TRN)”
key: linked_trn · SCA field: matter.linked_trn
Corrected (9 Sep 2026): live evidence confirmed the text box revealed by this branch is labelled "Reference number" on the real page, not "TRN" — the previous fictional label never matched any real <label>, so this field's own candidateCount was always 0 and it was reported as "could not be found on this page" even once its trigger correctly revealed it. Example placeholder only — no real TRNs are stored in this workspace.