NOD | Confirmation page - download PDF of completed submission

[eileen-coforma]

Value Statement

As a Veteran that has just submitted an appeal on VA.gov I want to download a copy of the information I submitted on the form in a PDF that looks like the paper form filled out So that I can retain it for may records and reference it if I need to recall what I submitted for future filing

---

Background Context

We want to provide a copy of the PDF back to Veterans after they submit. The PDF should be watermarked to prevent resubmissions. PDFs generated from lighthouse should take a few seconds, but could take up to a minute. The designs should account for the delay, as well as, possible failure.

Outcome, Success Measure, KPI(S), and Tracking Link

• CTA button click for NEW download event | Baseline: N/A | Target: TBD | Link to Data Source: TBD

Acceptance Criteria

• [ ] User can access the confirmation page regardless of the PDF being ready or not
• [ ] If the PDF link is not ready, user will know that a PDF link is generating
• [ ] If the link takes longer than 1 minute to load, a warning alert shows under the loading indicator to inform users of the delay
• [ ] When the PDF is ready, a link will be generated and screen reader users are notified that the link is ready
• [ ] When the user clicks a link, the PDF download will immediately start and the document will be downloaded to the user's computer
• [ ] User is notified if the PDF is not available for download.

Designs and Build Notes

• FIGMA

Enablement team (if needed)

@jstrothman

Out of scope

• Confirmation email
• .txt download
• Supplemental claim and HLR confirmation pages
• Other information on the confirmation page

Open questions

• How long does the PDF generation take (from LH)?
• What happens if PDF generation fails, or we can't reach the LH endpoint?
  • Error message
• How long of a delay is considered unacceptable and we show an error message?
  • Ask stakeholder. Timeout state 30s-1m?
  • From Julie: Delay message 1minute in (This is taking longer than expected)
• What happens when the rage clicking occurs?
  • Nothing currently, but we program link to ignore subsequent clicks
• What happens if user hard refreshes confirmation?
  • Shows confirmation without any data
  • Consider including a warning message about refreshing or leaving the page (separate ticket).

Tasks

• [ ] Task
• [ ] Task
• [ ] Task

Definition of Ready

• [ ] LH endpoint is available
• [ ] Clear value description
• [ ] Testable acceptance criteria
• [ ] Accessibility added to acceptance criteria
• [ ] Approved designs attached
• [ ] Sample data provided where appropriate
• [ ] Estimated to fit within the sprint
• [ ] Dependencies and blockers linked

Definition of Done

• [ ] Meets acceptance criteria
• [ ] Passed E2E testing (90% coverage)
• [ ] Passed unit testing (90% coverage)
• [ ] Passed integration testing (if applicable)
• [ ] Code reviewed (internal)
• [ ] Submitted to staging
• [ ] Team approved production verification process
• [ ] Reviewed and approved by product and/or design

[eileen-coforma]

@eileen-coforma confirm with Julie on timeout behavior.

[eileen-coforma]

Consider error state for PDF failure. Can it live outside of the blue box?

[eileen-coforma]

@saderagsdale @shaunburdick Updated the ticket with new AC for delay state. Designs have been updated to include a timeout state.

[eileen-coforma]

Blocked by LH endpoint availability

[dfong-adh]

No new fields, updates also on hold