arf/simple-forms-duplicate-and-add-686c

[patrick-brown-oddball]

Summary

We are adding a form upload to the Accredited Rep Portal. We are borrowing from simple forms but creating a new system for our needs. You can read more about the needs and reasoning here - https://dsva.slack.com/docs/T03FECE8V/F08GCG2AQ1H

We are releasing the app in steps. This is the first. The steps for the backend are -

• HERE add 21-686c form to persistent attachments and form upload notification email. We will re-use these already built parts for our own app. We are starting off our application with the 21-686c form as a baseline and then we are going to add the other forms once we are done with the infrastructure
• Make the upload tool ARP compliant - create our own controller with validations for our circumstances such as checking power of attorney for the claimant
• Add new table arp_in_progress_forms so any reps that are also veterans don't affect their own uploads

Related issue(s)

• vets-website pr - Create Simple Forms Upload Duplicate and add 21-686c vets-website#35338

• content-build pr - Create Simple Forms Upload Duplicate and add 686c content-build#2485

• collab cycle - Collaboration Cycle for Accredited Rep Facing (ARF) - Representative Form Upload va.gov-team#104783

• since we are borrowing from simple forms, the data flow diagram is the same - https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1702671758787/1eee327caf163786a70af458b56128b9e5b3ce2e?sender=954d567f-8d91-47d1-b8a4-ce33e64ea3a2

We will eventually add a power of attorney check on submit to make sure the rep has poa for the veteran they are submitting the form for. We are starting with the 686c form and then expand out to all the forms we need

Testing done

• New code is covered by unit tests

What areas of the site does it impact?

• A new page at /representative_form_upload

Acceptance criteria

• I added unit tests and integration tests for each feature