Sent-letter history and staff actions

Search Sent Letters History

Filter the AJAX history by the fields implemented in the dashboard controller.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard → Sent Letters History → Search

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

Filter the AJAX history by the fields implemented in the dashboard controller. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Enter part of a reference, subject, recipient name or recipient company.
Wait for the 300 ms delayed search.
Review the returned first page.
Clear the search to restore all records.

Fields, choices and supported possibilities

Action scopeFilter the AJAX history by the fields implemented in the dashboard controller.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard → Sent Letters History → Search

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 dashboard AJAX search checks reference_no, subject, recipient_name and recipient_company.
It does not search recipient email, phone, courier or tracking code in this endpoint.

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.