PDF generation, branding and files

Understand the letter verification barcode

Use the printed verification code as secondary visible evidence.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationOpen generated PDF → bottom digital security area

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

Use the printed verification code as secondary visible evidence. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Locate the Code 128 barcode near the end of the letter body.
Read the visible random verification code.
Compare it with the public verification page or client letter history.

Fields, choices and supported possibilities

Action scopeUse the printed verification code as secondary visible evidence.

Module version1.0.0

Exact routeOpen generated PDF → bottom digital security area

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 barcode encodes random_verification_code.
The model creates an eight-character uppercase code using an MD5/uniqid-based value.
This code is separate from the public unique_code and signature hash.

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.