Understand letter record edit, delete and void limitations
Avoid promising lifecycle controls that the supplied history UI does not implement.
Exact navigationAdmin Area → Letter Manager → Sent Letters History
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
Avoid promising lifecycle controls that the supplied history UI does not implement. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Exact step-by-step process
- Treat an issued record as retained evidence.
- If content is wrong, preserve the original under policy and create corrected correspondence.
- Use authorised database/retention procedures only when removal is legally approved.
Fields, choices and supported possibilities
Action scopeAvoid promising lifecycle controls that the supplied history UI does not implement.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Sent Letters History
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 supplied controller has no edit, delete, void, cancel or archive action for history records.
- The model exposes clear_signature but no controller route uses it in the supplied files.
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.
Important code-backed limitationDo not alter issued correspondence directly in the database to imitate a supported correction workflow.