PDF generation, branding and files

Understand Letter Manager subject and body layout

Check the highlighted subject box and HTML letter content in the PDF.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationGenerate PDF → subject box and main body

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

Check the highlighted subject box and HTML letter content in the PDF. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Confirm the subject appears uppercase in the centred bordered box.
Confirm the HTML body follows below with professional spacing.
Check page breaks, lists, links and long paragraphs.
Revise the source content and create a new letter if a formal issued record is wrong.

Fields, choices and supported possibilities

Action scopeCheck the highlighted subject box and HTML letter content in the PDF.

Module version1.0.0

Exact routeGenerate PDF → subject box and main body

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

Subject font is reduced to 10 pt in the active code.
Main letter body uses Helvetica 10 pt and writeHTML.
The module has no edit-and-regenerate action for an existing history record.

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.