Verify QR Code Compliance database readiness | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/verify-qr-code-compliance-database-readiness Publisher: Pixie Technologies LLC Installation, access and lifecycle Verify QR Code Compliance database readiness Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Confirm the compliance record and event tables exist before generating evidence. Audience: CRM staff; Permission: Staff login; Module v2.1.1; 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 Confirm the compliance record and event tables exist before generating evidence. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Go to QR Compliance Records. - Check the page readiness message. - If not ready, reactivate/upgrade the module through Setup → Modules. - Generate a test PDF only after readiness is confirmed. Fields and options Action scopeVerify the compliance record and event tables exist before generating evidence. 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 model is_ready check requires both module-owned tables. 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 QR Code Compliance module overview (https://pixiecrm.com/help-centre/qr-code-compliance-module-overview)Understand QR Code Compliance routes (https://pixiecrm.com/help-centre/understand-qr-code-compliance-routes)Understand QR Code Compliance migrations (https://pixiecrm.com/help-centre/understand-qr-code-compliance-migrations)Deactivate QR Code Compliance with data-loss warning (https://pixiecrm.com/help-centre/deactivate-qr-code-compliance-with-data-loss-warning)Export invoices and sales PDFs (https://pixiecrm.com/help-centre/export-invoices-and-sales-pdfs)Create a credit note (https://pixiecrm.com/help-centre/create-a-credit-note)