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

Include specific 21-22a authorizations (Fields 19a and 19b) in PDF generation #96908

Closed
3 tasks
oddball-lindsay opened this issue Nov 12, 2024 · 5 comments
Closed
3 tasks
Assignees
Labels
accredited-representation-management-team Accredited Representation Management team backend mvp Initial version of thing

Comments

@oddball-lindsay
Copy link
Contributor

oddball-lindsay commented Nov 12, 2024

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

  • Ensure the 21-22a PDF has field 19a completed, based on user input
  • Ensure the 21-22a PDF has field 19b completed, based on user input

Acceptance Criteria

  • The 21-22a generated PDF has fields 19a and 19b filled out, based on the user's input in the Appoint a Rep experience.
@oddball-lindsay oddball-lindsay added backend mvp Initial version of thing accredited-representation-management-team Accredited Representation Management team labels Nov 12, 2024
@oddball-lindsay oddball-lindsay changed the title Backend: accept authorizations for 21-22a field 19, to fill out PDF Include specific 21-22a authorizations (Field 19) in PDF generation Nov 12, 2024
@oddball-lindsay oddball-lindsay changed the title Include specific 21-22a authorizations (Field 19) in PDF generation Include specific 21-22a authorizations (Fields 19a and 19b) in PDF generation Nov 12, 2024
@opticbob
Copy link

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.

@opticbob
Copy link

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 ?

@oddball-lindsay
Copy link
Contributor Author

@opticbob hmmm good point on the frontend we simply ask yes or no for the 19a field:
Image

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:

  • Attorneys have a "Organization" field in the Trexler File but it is null for most (if not all) of them. And I'm not seeing that field at all for claims agents. It doesn't seem like we have a straightforward path to know the associated firm/organization for an attorney or claims agent.
  • This is not required to process a form, although it may affect how the attorney can support the Veteran/claimant.
  • 21-22a is not opening up to digital submission anytime soon, so there is room for the attorney to update when they sign the form in a non-digital manner.

I could see two solutions at the moment:

  1. Simply check the box and leave the input blank -- when the Veteran/claimant brings the form in (or mails it in), the attorney or claims agent can complete this before signing if they want to.
  2. Add some general content like [accredited representative name]'s associated firm/organization.

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!

@opticbob
Copy link

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.

@opticbob
Copy link

The PR for this ticket has been approved and merged.

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 backend mvp Initial version of thing
Projects
None yet
Development

No branches or pull requests

2 participants