Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Text inputs are not pre-populating with Profile information (auth users) #96836

Closed
oddball-lindsay opened this issue Nov 11, 2024 · 4 comments
Closed
Assignees
Labels
accredited-representation-management-team Accredited Representation Management team bug Something isn't working frontend mvp Initial version of thing

Comments

@oddball-lindsay
Copy link
Contributor

oddball-lindsay commented Nov 11, 2024

Expected vs. Actual

Expected: Information from authenticated users' Profile is pre-populated in the text inputs, of the Appoint form-fill experience. Similar to the 26-4555 experience for authenticated users.

Actual: Text inputs are blank for all users, including authenticated users who definitely have personal and contact information in their Profile.

Affected screens:

  • claimant-personal-information

  • claimant-contact-mailing

  • claimant-contact-phone-email

  • veteran-personal-information

  • veteran-contact-mailing

  • veteran-contact-phone-email

  • veteran-identification

  • veteran-service (unsure if we have this "branch of service" information in a user's Profile -- there is a section that says "military information" but I was unable to find a test user that had this information available)

Steps to Reproduce

For the non-Veteran pathway:

  1. Login with one of our ARM test users for Appoint. An LOA3 user would be best, as they have more information in their Profile (LOA1 users may only have an email address in their Profile)
  2. Select "I'm not the Veteran"
  3. Navigate through to the Claimant chapter
  4. Observe that text inputs are blank

For the Veteran pathway:

  1. Login with one of our ARM test users for Appoint. An LOA3 user would be best, as they have more information in their Profile (LOA1 users may only have an email address in their Profile)
  2. Select "I'm the Veteran"
  3. Navigate through to the Veteran chapter
  4. Observe that text inputs are blank

Next Steps

@oddball-lindsay oddball-lindsay added accredited-representation-management-team Accredited Representation Management team bug Something isn't working frontend mvp Initial version of thing labels Nov 11, 2024
@raudabaugh
Copy link

raudabaugh commented Nov 12, 2024

Some potential leads for fixing this:

  1. Are the form profile mappings mismatched? (e.g. seeing email here vs. emailAddress here)
  2. Should this returnUrl match one of the chapter paths?
  3. Could the staging test users be failing identity validation (do they have PIDs)?
  4. Try setting the verifyRequiredPrefill option to true

@oddball-lindsay
Copy link
Contributor Author

The Authenticated Experience Design team recommended reaching out to Adam Whitlock for help, he is the Lead FE Engineer on the team and it sounds like he has been working with the Profile code for a while.

@jvcAdHoc
Copy link
Contributor

draft pr for front end. I need to add unit tests.

@oddball-lindsay
Copy link
Contributor Author

Tested with both the "I'm the Veteran" and "I'm not the Veteran" pathway, confirming the relative Veteran/Claimant chapter text inputs are pre-populated based on that up-front selection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accredited-representation-management-team Accredited Representation Management team bug Something isn't working frontend mvp Initial version of thing
Projects
None yet
Development

No branches or pull requests

3 participants