Bulk export and operational limitations

Prepare the e-Invoice temporary folder

Meet the exporter writability requirement and automatic cleanup flow.

Audience: CRM staffPermission: Server administrator plus e-Invoice: Bulk ExportModule v1.0.0
Exact navigationServer deployment → CRM TEMP_FOLDER, then Admin Area → Utilities → Bulk Export
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

Meet the exporter writability requirement and automatic cleanup flow. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Exact step-by-step process

  1. Confirm TEMP_FOLDER exists and is really writable by PHP.
  2. Use directory permission 0755 where appropriate to the hosting model.
  3. Run a controlled export.
  4. Confirm the exporter work directory is removed by shutdown cleanup.

Fields, choices and supported possibilities

Action scopeMeet the exporter writability requirement and automatic cleanup flow.
Module version1.0.0
NavigationServer deployment → CRM TEMP_FOLDER, then Admin Area → Utilities → Bulk Export
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • The constructor throws a RuntimeException when TEMP_FOLDER is not writable.
  • The exporter refuses to clear TEMP_FOLDER itself and creates a type-specific working directory with 0755.

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.