Understand recipient-window formatting
Verify the person, organisation and address lines rendered in the PDF receiver 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.
Where to goGenerate PDF → top receiver window
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 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.
Follow these steps
- Generate a test for a customer and an external recipient.
- Verify person name is shown first when available.
- Verify company is prefixed with M/S where applicable.
- Verify address lines are cleaned, deduplicated and compacted.
- Correct source data if the receiver block is wrong.
Fields and options to review
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.
Rules the system enforces
- 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.
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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.