Installation, access and lifecycle

Verify QR Code Compliance database readiness

Confirm the compliance record and event tables exist before generating evidence. 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 v2.1.1
Jump to steps
Where to goAdmin Area → QR Compliance Records
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

Confirm the compliance record and event tables exist before generating evidence. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Go to QR Compliance Records.
  2. Check the page readiness message.
  3. If not ready, reactivate/upgrade the module through Setup → Modules.
  4. Generate a test PDF only after readiness is confirmed.

Fields and options to review

Action scopeVerify the compliance record and event tables exist before generating evidence.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • The model is_ready check requires both module-owned tables.

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.