Api 33481 poa v2 ind signatures

[acovrig]

Summary

• Require registrationNumber
• Validate regNum
• Add the signature to the generated PDF

Related issue(s)

• API-33481

Testing done

• New code is covered by unit tests
• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing
• If this work is behind a flipper:
  • Tests need to be written for both the flipper on and flipper off scenarios. Docs.
  • What is the testing plan for rolling out the feature?

What areas of the site does it impact?

v2 individual POA

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature

[jvcAdHoc]

we could probably remove first and last name from here. That would require adding them back into the form data like what you did for 2122.

[jvcAdHoc]

Nice, I like this language update