Campaign content and validation

Understand newsletter template HTML preparation

This guide explains that how complete HTML templates are reduced to email-body content before editing and delivery.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Jump to steps
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 this guide helps you do

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

  1. Select a predefined template.
  2. Check the copied body in the editor.
  3. Correct any layout that relied on stripped page-level markup.
  4. Send a controlled test campaign before a large distribution.

Fields and options

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 and limits

  • 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.

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.