Sent-letter history and staff actions

Page through Sent Letters History

Use the server-side ten-record pagination controls.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Sent Letters History → page numbers

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 server-side ten-record pagination controls. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Open Sent Letters History.
Select a page number.
Use search to reduce the result set when needed.
Remember checkbox selection applies only to currently rendered rows.

Fields, choices and supported possibilities

Action scopeUse the server-side ten-record pagination controls.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Sent Letters History → page numbers

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

per_page is 10.
Results are ordered by history ID descending.
The response page count uses ceil(max(1,total)/10).

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.