Verify Letter Manager v1.0.0 after deployment
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to run an end-to-end acceptance test covering every critical live branch.
Where to goStaging/controlled production test → Letter Manager
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 this guide helps you do
Run an end-to-end acceptance test covering every critical live branch. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Create, edit, apply and delete a test template.
- Create one client-linked and one external letter.
- Test PDF branding, QR and verification code.
- Test email note and each enclosure validation branch.
- Test successful send, missing target, resend and read receipt.
- Test required signature and signed evidence.
- Test public field settings.
- Test history search/pagination/actions.
- Test single and bulk postal update.
- Test admin customer history and two isolated client accounts.
- Record all results against module version 1.0.0.
Fields and options
Action scopeRun an end-to-end acceptance test covering every critical live branch.
Module version1.0.0
Exact routeStaging/controlled production test → Letter Manager
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- 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.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.