Understand QR public token generation
Know how the 64-character public URL token is created and checked.
Exact navigationAutomatic record creation → Public signing URL
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 how the 64-character public URL token is created and checked. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Generate a supported PDF.
- Open the admin record.
- Use the public URL provided by the module; do not construct a token manually.
Fields, choices and supported possibilities
Action scopeKnow how the 64-character public URL token is created and checked.
Module version2.1.0
NavigationAutomatic record creation → Public signing URL
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- The model creates a lowercase 64-hex token from secure random bytes with a fallback and up to five uniqueness attempts.
- The public controller rejects tokens not matching exactly 64 lowercase hexadecimal characters.
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.