-
Notifications
You must be signed in to change notification settings - Fork 213
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
21-22: Authorizations in PDF do not reflect user's input #96847
Comments
The "all authorized" and "none authorized" experiences seem to be filling the form out as expected. I'm not sure though if the "some authorized" is quite right for the medical experience. If I authorize only Drug Abuse in Appoint, then the form has only Drug Abuse checked in Field 20. But the way that field is phrased, it seems like Drug Abuse should actually be the only box unchecked and all other boxes should be checked as an "opt out" concept. Sent an email to stakeholders to confirm what the right way to approach this is. |
After checking with stakeholders, we do need to take the opposite approach for Field 20 on the 21-22. It's tricky because the frontend asks which records the Veteran wants to disclose. But then the backend on the form needs to check the opposite records, indicating (again on the form) which records should not be disclosed. Expectation: Steps to Reproduce:
@cosu419 @opticbob is this a frontend fix, where we change what is passed to the backend? Or is this a backend fix, where we change how the backend interprets what the frontend is currently sending over? |
Chatted in standup and this is a backend fix, so we'll tackle that update over in #98295 |
Expected vs. Actual
Expected: The PDF download should have the appropriate authorizations specified, based on the user's input in the Appoint experience.
Actual: The PDF download doesn't seem to check any boxes, despite saying yes to the medical and address authorizations in the Appoint experience.
It seems this is because the frontend is not sending the boolean values to the backend.
Steps to Reproduce
Approving authorizations:
The text was updated successfully, but these errors were encountered: