Create a QR compliance record by generating a PDF
Trigger get-or-create through the supported PDF close hook. 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 → Sales → Open supported document → View or download PDF
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
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.
Follow these steps
- Enable compliance and the relevant document QR setting.
- Go to an invoice, payment, credit note, estimate or proposal.
- Generate its PDF.
- Go to QR Compliance Records and locate the new pending record.
Fields and options to review
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
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- 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.
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.