PDF generation, branding and files

Understand the PDF header and footer

Review reference, company contact, verification code and page numbering added automatically.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationGenerated PDF → header and footer

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

Review reference, company contact, verification code and page numbering added automatically. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Check the reference and company name in the header.
Check company address, phone and website in the header.
Check the footer verification code or fallback reference.
Check Page X of Y numbering.

Fields, choices and supported possibilities

Action scopeReview reference, company contact, verification code and page numbering added automatically.

Module version1.0.0

Exact routeGenerated PDF → header and footer

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

Header and Footer are implemented by the LetterPDF class.
The footer uses random_verification_code and can fall back to reference_no.

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.