Insert legacy QR merge fields
Build non-compliance QR content from the supported document, client and other merge fields. 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 → Setup → Settings → QR Code Compliance → document tab → QR Code Info
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
Build non-compliance QR content from the supported document, client and other merge fields. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Disable compliance mode only when legacy QR content is required.
- Go to the required document tab.
- Place the cursor in QR Code Info.
- Select merge fields from the supplied document/client/other lists.
- Save and test output.
Fields and options to review
Action scopeBuild non-compliance QR content from the supported document, client and other merge fields.
Module version2.1.0
NavigationAdmin Area → Setup → Settings → QR Code Compliance → document tab → QR Code Info
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- Merge-field text is processed only on the legacy fallback path.
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.