PDF generation, branding and files

Understand the PDF company closing block

Verify the automatically appended Best regards company block. 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.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goGenerated PDF → end of letter content

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

Verify the automatically appended Best regards company block. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Check the company name.
Check the two-line company address.
Check phone and website values.
Correct CRM company settings and generate a new test letter if needed.

Fields and options to review

Action scopeVerify the automatically appended Best regards company block.

Module version1.0.0

Exact routeGenerated PDF → end of letter content

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

The closing block is appended after stored letter content.
It is not part of the editable TinyMCE body.

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.

Was this guide useful?Your response is stored only in this browser.