Understand newsletter template HTML preparation
Know how complete HTML templates are reduced to email-body content before editing and delivery.
Exact navigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Predefined Templates
Before you begin
- 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 covers
Know how complete HTML templates are reduced to email-body content before editing and delivery. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Select a predefined template.
- Review the copied body in the editor.
- Correct any layout that relied on stripped page-level markup.
- Send a controlled test campaign before a large distribution.
Fields, choices and supported possibilities
Action scopeKnow how complete HTML templates are reduced to email-body content before editing and delivery.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Predefined Templates
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- The preparation routine decodes HTML entities, removes doctype, html, head, meta, title and script wrappers, extracts style blocks and preserves the CSS with the body content.
- Executable script content is not retained in the newsletter editor.
Expected result and verification
- 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.