Use the floating QR Compliance document button
Follow this guide to open an existing compliance record from supported admin document pages. 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 → Open supported invoice/payment/credit note/estimate/proposal → QR Compliance
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
Open an existing compliance record from supported admin document pages. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Go to a supported document page.
- Select the floating QR Compliance button.
- If the record exists, review it.
- If warned that no record exists, generate the PDF first.
Fields and options to review
Action scopeOpen an existing compliance record from supported admin document pages.
Module version2.1.0
NavigationAdmin Area → Open supported invoice/payment/credit note/estimate/proposal → QR Compliance
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- The injected button recognises supported admin URL/hash patterns.
- It does not create the record; PDF generation does.
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.