Campaign content and validation

Validate newsletter subject, body and recipients

Resolve every server-side condition checked before a campaign record is created.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Exact navigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Start Newsletter Send
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

Resolve every server-side condition checked before a campaign record is created. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Exact step-by-step process

  1. Confirm the subject is not blank.
  2. Confirm the body contains visible content.
  3. Confirm at least one recipient key is selected.
  4. Confirm each selected key still resolves to an eligible valid email.
  5. Submit the campaign.

Fields, choices and supported possibilities

Action scopeResolve every server-side condition checked before a campaign record is created.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Start Newsletter Send
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • No campaign is created when there are no valid resolved recipients.

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.