Record creation, snapshots and PDF output

Create a QR compliance record by generating a PDF

Trigger get-or-create through the supported PDF close hook.

Audience: CRM staffPermission: Administrator or authorised staff with normal document accessModule v2.1.1
Exact navigationAdmin Area → Sales → Open supported document → View or download 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

Trigger get-or-create through the supported PDF close hook. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Exact step-by-step process

  1. Enable compliance and the relevant document QR setting.
  2. Open an invoice, payment, credit note, estimate or proposal.
  3. Generate its PDF.
  4. Open QR Compliance Records and locate the new pending record.

Fields, choices and supported possibilities

Action scopeTrigger get-or-create through the supported PDF close hook.
Module version2.1.0
NavigationAdmin Area → Sales → Open supported document → View or download PDF
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • Generating the PDF is the creation trigger; there is no separate Create Record form.
  • The unique document-type/document-ID rule reuses an existing record.

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.