-
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
Include specific 21-22a authorizations (Fields 19a and 19b) in PDF generation #96908
Comments
The first thing to do here is to determine what the shape of the additional frontend request data will look like. I plan to ping @cosu419 in the morning to discuss it. |
I made a plan with @cosu419 for how we would send the question 19 data between the frontend and backend. As of right now I can check both boxes and fill text in both fields. I'll ask this in slack tomorrow but this is a preview. Are we planning on collecting the text field for 19a on the frontend? The prompt for that is Provide the name of the firm/organization here:. We do have a screen where we'll be collecting the names for the 19b text field. The prompt for that one is Provide the names of the individuals here: @cosu419 showed me that screen but it sounded like we didn't have one for the 19a text field. What do you think @oddball-lindsay ? |
@opticbob hmmm good point on the frontend we simply ask yes or no for the 19a field: But the 21-22a is looking for the name of the firm/organization to be entered in, in addition to the box being checked. Some things to consider:
I could see two solutions at the moment:
I'm not sure how acceptable Option 2 is so I'm leaning towards Option 1. If you open this discussion up on Slack, I'm very curious to hear other's input! |
In regards to the above comment we are going with solution 1, checking the box and leaving it to be filled in by the accredited individual when they meet with the veteran/claimant. The PR for this was marked ready for review today and I've requested a review from the team. |
The PR for this ticket has been approved and merged. |
The 21-22a form has unique authorizations (Field 19a and 19b) that we need to make sure to fill out, based on the user's input.
The frontend should be passing this to the backend in #96848. And the backend will need to add the input to the 21-22a PDF when it is generated.
Tasks
Acceptance Criteria
The text was updated successfully, but these errors were encountered: