Closed holdenhinkle closed 2 weeks ago
Can't really test the auth state without prefill configured on vets-api - @mtri can you check the unauth state?
Unauth state looks good.
Awaiting the ability to pre-fill when possible
8/8 update: part of an active PR with CI checks that need to be addressed. Also pending the prefill functionality vets-api ticket.
8/12 update: CI checks passing, PR pending review
Looking into the prefill response - expecting the auth state to be triggered for users with profile information available.
Rendering the auth state is wrapped up in the same issue as Claimant Contact Information. Need to figure out why formData.veteran
is empty for test users.
I ran out of time today -- to do for me: create a similar ticket that focuses on the prefill pattern and carry over Colin's notes above. Then link that ticket here for continuity and close this ticket out.
Assigning myself as a reminder to come back to this ticket :).
Here's the ticket for the prefill pattern, which will be in Product Backlog for a future time https://github.com/department-of-veterans-affairs/va.gov-team/issues/90986.
Issue Description
The Claimant Personal Information page will be available to:
Content is dynamic based on:
~1. If the auth user has all of the required information (first name, last name, date of birth) in their profile show the authenticated design~ (Saving this for https://github.com/department-of-veterans-affairs/va.gov-team/issues/90986)
The information collected on this page will be routed to the forms as follows:
URL:
/claimant-personal-information
Previous paths:
/claimant-relationship
Next paths:
/claimant-contact
(non-Veteran auth with all required info on file)~ (Saving this for https://github.com/department-of-veterans-affairs/va.gov-team/issues/90986)/claimant-contact-phone-email
(all other non-Veteran users)MVP Planning Mural
"Auth" Designs (Prefill)
Prototype, Canvas, Annotations
Disclaimer: We only designed the authenticated experience for a Veteran user. In a case where we have a non-Veteran claimant that sees this authenticated experience, we'd only need to display the first name, last name and date of birth. SSN, Branch of Service and VA File Number are not required in the Claimant section of the 21-22 and 21-22a.
Screenshots
"Unauth" Designs (Input fields)
Prototype, Canvas
Screenshots
Tasks
Acceptance Criteria