Understand deactivation and removal limitations
Avoid assuming that the supplied release automatically removes its database tables or campaign data. 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 → Setup → Modules → Email Marketing / Newsletter
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
Avoid assuming that the supplied release automatically removes its database tables or campaign data. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Export or retain any campaign evidence required by policy.
- Deactivate the module only through Setup → Modules.
- Check the Letter Manager tab and cron handler stop loading.
- Use an approved database change only if the organisation intentionally removes retained module data.
Fields and options to review
Action scopeAvoid assuming that the supplied release automatically removes its database tables or campaign data.
Module version1.0.0
NavigationAdmin Area → Setup → Modules → Email Marketing / Newsletter
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- The supplied code has an activation hook but no registered deactivation or uninstall cleanup hook.
- Do not manually drop tables as part of routine deactivation.
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.