Search Sent Letters History
Follow this guide to filter the AJAX history by the fields implemented in the dashboard controller. 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 goAdmin Area → Letter Manager → Dashboard → Sent Letters History → Search
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
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.
Follow these steps
- Enter part of a reference, subject, recipient name or recipient company.
- Wait for the 300 ms delayed search.
- Check the returned first page.
- Clear the search to restore all records.
Fields and options to review
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.
Rules the system enforces
- 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.
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.