Understand Letter Manager PDF filenames
Locate the generated file based on the letter reference. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goServer filesystem → uploads/letter_manager/Letter_{reference}.pdf
Before you start
- Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
- Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.
What you’ll accomplish
Locate the generated file based on the letter reference. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Copy the letter reference.
- Verify the file name is Letter_{reference}.pdf.
- Use the UI rather than guessing a URL for normal access.
- Include the file in authorised backups and retention processes.
Fields and options to review
Action scopeLocate the generated file based on the letter reference.
Module version1.0.0
Exact routeServer filesystem → uploads/letter_manager/Letter_{reference}.pdf
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules the system enforces
- generate_and_send writes the PDF in FCPATH/uploads/letter_manager.
- Resending regenerates and overwrites the same reference-based path.
How to confirm it worked
- The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
- The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
- Any warning, missing file or failed send is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify recipient identity before sending or exposing public links.
- Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
- Test configuration and deployment changes with controlled records before production-wide use.
- Interpret email opens and e-signatures according to their documented technical limitations.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.