Understand unsupported Letter Manager features
Set accurate expectations for v1.0.0.
Exact navigationLetter Manager module overview
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
Set accurate expectations for v1.0.0. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Exact step-by-step process
- Use client/external creation, templates, PDFs, email, signature, verification, read tracking, history, tasks and postal tracking as documented.
- Do not expect draft status, approval workflow, scheduled sending, bulk letter generation, merge fields, editing, voiding, deletion, token expiry, courier API tracking or delivery-bounce processing.
- Evaluate future releases before updating user guidance.
Fields, choices and supported possibilities
Action scopeSet accurate expectations for v1.0.0.
Module version1.0.0
Exact routeLetter Manager module overview
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
- Only the values and actions exposed by the supplied Letter Manager v1.0.0 code are supported.
- Browser controls are not a substitute for server-side and operational verification.
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.