Understand QR record statuses
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Interpret pending and signed states used by the live model and filters.
Where to goAdmin Area → QR Compliance Records
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 this guide helps you do
Interpret pending and signed states used by the live model and filters. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Filter by Pending for records awaiting signature.
- Filter by Signed for locked evidence.
- Go to a record for full status details.
Fields and options
Action scopeInterpret pending and signed states used by the live model and filters.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- The supplied admin filter accepts All, pending and signed.
- No revoke, expired or deleted status is implemented.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.