PDF generation, branding and files

Understand recipient-window formatting

Verify the person, organisation and address lines rendered in the PDF receiver block.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationGenerate PDF → top receiver window

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

Verify the person, organisation and address lines rendered in the PDF receiver block. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Generate a test for a customer and an external recipient.
Confirm person name is shown first when available.
Confirm company is prefixed with M/S where applicable.
Confirm address lines are cleaned, deduplicated and compacted.
Correct source data if the receiver block is wrong.

Fields, choices and supported possibilities

Action scopeVerify the person, organisation and address lines rendered in the PDF receiver block.

Module version1.0.0

Exact routeGenerate PDF → top receiver window

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

The active v9 helper is used when available, with a MultiCell fallback.
Helper logic attempts to identify and swap company-like values when person/company fields are reversed.
Numeric-only and duplicate address fragments may be omitted.

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.