Understand newsletter template HTML preparation
This guide explains that how complete HTML templates are reduced to email-body content before editing and delivery. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Letter Manager → Email Marketing / Newsletter → Predefined Templates
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 you’ll accomplish
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.
Follow these steps
- Select a predefined template.
- Check 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 and options to review
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
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- 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.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.