PDF generation, branding and files

Regenerate a letter PDF when resending email

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains that Resend Email reruns PDF generation before sending.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goAdmin Area → Letter Manager → Sent Letters History → Resend Email

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 this guide helps you do

Understand that Resend Email reruns PDF generation before sending. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Go to the existing internal view and record the current stored data.
Select Resend Email.
Reopen the PDF and confirm it was generated successfully.
Check the email status and sent timestamp.

Fields and options

Action scopeUnderstand that Resend Email reruns PDF generation before sending.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Sent Letters History → Resend Email

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Rules and limits

resend_email calls generate_and_send(id).
The same reference-based PDF path is written again.
The resend uses the current history record and current company settings.

Check 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.