Understand legacy fallback when record creation fails
This guide explains that why a PDF may contain configured merge-field content instead of a signing URL. 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, then generate 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
Know why a PDF may contain configured merge-field content instead of a signing URL. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Verify compliance and the document type are enabled.
- Check module tables are ready.
- Generate the PDF.
- If record creation fails, review logs and the QR content.
Fields and options to review
Action scopeKnow why a PDF may contain configured merge-field content instead of a signing URL.
Module version2.1.0
NavigationAdmin Area → Setup → Settings → QR Code Compliance, then generate PDF
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- The service logs the record-creation failure and falls back to legacy merged content rather than stopping PDF generation.
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.