8.4 — View/Download Later

# 8.4 — View/Re-Download from Documents List (MVP)

**Priority (MoSCoW):** Must
**Persona:** Qualified Supplier (recipient) / Registry Analyst (staff visibility)
**Value:** Applicants can access their Verification Statement again at any time from the filing record, so they don’t need to rely only on the first email or mailed copy.

---

## User Story
As a **qualified supplier**, I want to **re-download my Verification Statement from the filing’s Documents list**, so that **I always have access to my official record if I misplace the original**.

## Context
- **Where:** Filing Request → Documents list.
- **Before:** Filing request is Filed and a Verification Statement has been created and delivered (Stories 8.2 and 8.3).
- **After:** The Verification Statement appears in the Documents list for that filing. The applicant can open or re-download it at any time.
- **Policy fit (BA to confirm):**
- FOIPPA: Only the submitting party can see and download the document.
- Manufactured Home Act — s. 8(1): Registrar must file a record if it appears to comply.
**How this story meets it:** Document is tied to the filing record and accessible to the filer as proof.

## UX/UI Link (Design-owned)
_To be added by **Design** (after BA review is complete)._

## MVP Boundary (story-level; PO-owned)
- **In:**
- Display the Verification Statement in the Documents list for the filing.
- Allow applicants to view and download the PDF again at any time.
- Record audit entries when the document is downloaded.
- **Out:**
- Document expiry, link expiry, or complex permissions.
- Bulk download of multiple documents.
- Delivery retry logic (covered in 8.3 Post-MVP).

---

## Acceptance Criteria (PO-owned; user-observable)
- [ ] Verification Statement appears in the Documents list for the filing.
- [ ] Applicant can open and download the PDF again.
- [ ] Staff can see that the Verification Statement exists in the Documents list.
- [ ] Each download is logged in the audit (who downloaded, when).
- [ ] **Accessibility:** Links are clear, keyboard reachable, focus visible, and announced to AT.
- [ ] **Unavailable:** If the document cannot be downloaded, a plain-language message is shown and the filing record remains valid.

---

## BA Section
*(BA responsible, Design consulted — SM enforces DoR)*

### Definition of Ready — BA gate
- [ ] Rules + edge cases + error/**Unavailable** complete
- [ ] Draft Gherkin (happy path + key errors)
- [ ] Policy refs confirmed & linked in Context
- [ ] Reviewed with Design; labels/states aligned
- [ ] UX/UI link pasted (Design)

---

**BA — please cover**
- [ ] What label should appear in the Documents list (exact wording)?
- [ ] Should applicants see file size/date generated?
- [ ] What should staff see if they open the Documents list?
- [ ] Error wording if the document cannot be retrieved.
- [ ] Confirm FOIPPA compliance — only the submitting party sees the file.

**Policy references (BA to confirm)**
- Manufactured Home Act — s. 8(1): Registrar must file record if it appears to comply. [Link](https://www.bclaws.gov.bc.ca/civix/document/id/complete/statreg/03075_01)
- FOIPPA — filer-only access; no public links.

**BA Prompts (things to think about)**
- How long should the Verification Statement remain available (forever for this filing, or time-limited)?
- What message should show if the document is missing or deleted?
- Do we need to log every download attempt, or only successful ones?
- Should the Documents list show delivery methods (download, email, mail) or just the file itself?

---

### BA — Edge cases Oge to confirm
| Edge case | What triggers it | What the user sees | Can they continue? |
|-----------------------------|-------------------------------------------|----------------------------------------------------------------------|--------------------|
| Document missing | Statement link exists but file not found | Error: “Verification Statement not available. Please contact Registry.” | No |
| Download service unavailable| Temporary system issue | Message: “Download unavailable. Please try again later.” | Retry later |

---

### BA — Gherkin (to draft before Dev)
- **Happy path**
Given a filing has a Verification Statement in the Documents list

- **Missing document**
Given the Verification Statement link exists but the file is missing

- **Unavailable**
Given the system is down
”

---

## Design — Prompts
- Confirm placement/label of the Verification Statement in the Documents list.
- Confirm whether to show extra details (file size, date created).
- Ensure accessibility basics (keyboard path, focus order, AT announcements).
- Paste design link above.