General and document settings

Understand QR PDF positioning

This guide explains that when the renderer uses configured X/Y coordinates or the current automatic PDF position. 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.

Audience: CRM staffPermission: Staff loginModule v2.1.1
Jump to steps
Where to goAdmin Area → Setup → Settings → QR Code Compliance → document tab
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 when the renderer uses configured X/Y coordinates or the current automatic PDF position. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Enter both numeric X and Y values for fixed placement.
  2. Otherwise leave one or both blank.
  3. Generate the PDF and inspect page flow.

Fields and options to review

Action scopeKnow when the renderer uses configured X/Y coordinates or the current automatic PDF position.
Module version2.1.0
NavigationAdmin Area → Setup → Settings → QR Code Compliance → document tab
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • When either configured coordinate is missing, the service inserts two line breaks and uses the PDF current available X/Y position.

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.