PDF generation, branding and files

Understand Letter Manager PDF filenames

Locate the generated file based on the letter reference.

Audience: Administrators and developersPermission: Authenticated staff accountModule v1.0.0

Exact navigationServer filesystem → uploads/letter_manager/Letter_{reference}.pdf

Before you begin

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 this guide covers

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.

Exact step-by-step process

Copy the letter reference.
Confirm 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, choices and supported possibilities

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.

Code-backed validations and workflow rules

generate_and_send writes the PDF in FCPATH/uploads/letter_manager.
Resending regenerates and overwrites the same reference-based path.

Expected result and verification

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.