Verify QR record integrity
Run the model checks for signature hash, snapshot fingerprint, evidence HMAC and verification code.
Exact navigationAdmin Area → QR Compliance Records → Open signed record
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
Run the model checks for signature hash, snapshot fingerprint, evidence HMAC and verification code. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Open a signed record.
- Read the PASS/FAILED integrity indicator.
- If failed, stop relying on the stamp and investigate the record/database history.
Fields, choices and supported possibilities
Action scopeRun the model checks for signature hash, snapshot fingerprint, evidence HMAC and verification code.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records → Open signed record
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- All four evidence components must match for integrity to pass.
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.