History, delivery and read evidence

Search and page Newsletter History

Follow this guide to filter campaigns by subject or status and use the server pagination limits. 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.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Jump to steps
Where to goAdmin Area → Letter Manager → Email Marketing / Newsletter → Newsletter History
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

Filter campaigns by subject or status and use the server pagination limits. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Enter a subject fragment or status in Search.
  2. Press Enter or trigger the search control.
  3. Select a supported page size.
  4. Move between result pages.

Fields and options to review

Action scopeFilter campaigns by subject or status and use the server pagination limits.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Newsletter History
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • The controller clamps page size to 1–50 and defaults to 10.

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.