Record creation, snapshots and PDF output

Understand legacy fallback when record creation fails

Know why a PDF may contain configured merge-field content instead of a signing URL.

Audience: CRM staffPermission: Staff loginModule v2.1.1
Exact navigationAdmin Area → Setup → Settings → QR Code Compliance, then generate 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

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.

Exact step-by-step process

  1. Confirm compliance and the document type are enabled.
  2. Check module tables are ready.
  3. Generate the PDF.
  4. If record creation fails, review logs and the QR content.

Fields, choices and supported possibilities

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
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • The service logs the record-creation failure and falls back to legacy merged content rather than stopping PDF generation.

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.