Verify Letter Manager dependencies
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Confirm the existing Letter Manager page, template selector and editor elements required by the injected newsletter workspace.
Where to goAdmin Area → Letter Manager
Before you start
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What this guide helps you do
Confirm the existing Letter Manager page, template selector and editor elements required by the injected newsletter workspace. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Go to Letter Manager.
- Verify the normal Letter Manager tabs and template dropdown load.
- Select the newsletter tab.
- Verify the module can read the existing template dropdown and initialise its editor.
Fields and options
Action scopeVerify the existing Letter Manager page, template selector and editor elements required by the injected newsletter workspace.
Module version1.0.0
NavigationAdmin Area → Letter Manager
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- The module looks for #template_id_external and falls back to #template_id.
- Predefined template copying depends on data-subject and data-letter-body attributes on the Letter Manager options.
Check it worked
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.
Related guides
Was this guide useful?Your response is stored only in this browser.