Troubleshooting and limitations

Troubleshoot a missing verified QR stamp

Separate pending status, disabled stamp, integrity failure and placement causes.

Audience: CRM staffPermission: Staff loginModule v2.1.1
Exact navigationAdmin Area → QR Compliance Records → record, then source document → PDF
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

Separate pending status, disabled stamp, integrity failure and placement causes. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Exact step-by-step process

  1. Confirm the record is signed.
  2. Confirm integrity PASS.
  3. Enable Verified stamp.
  4. Verify automatic or complete manual coordinates.
  5. Regenerate the PDF.

Fields, choices and supported possibilities

Action scopeSeparate pending status, disabled stamp, integrity failure and placement causes.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records → record, then source document → PDF
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • Only values and transitions exposed by the supplied module code are supported.
  • Server-side validation remains authoritative even when browser controls appear to accept a value.

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.