Understand QR Code Compliance migrations
Know the supplied 1.0.1, 1.0.2, 2.0.0 and 2.1.0 migration sequence without presenting migration internals as user features.
Exact navigationAdmin Area → Setup → Modules → QR Code Manager → Upgrade Database
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 the supplied 1.0.1, 1.0.2, 2.0.0 and 2.1.0 migration sequence without presenting migration internals as user features. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Confirm the installed module version.
- Use the module database-upgrade control when shown.
- Reopen settings and records after the upgrade.
Fields, choices and supported possibilities
Action scopeKnow the supplied 1.0.1, 1.0.2, 2.0.0 and 2.1.0 migration sequence without presenting migration internals as user features.
Module version2.1.0
NavigationAdmin Area → Setup → Modules → QR Code Manager → Upgrade Database
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- Migrations 101/102 extend earlier payment/base64 settings; 200/210 establish the compliance schema used by version 2.1.0.
- Version 2.1.1 adds Migration 211, which requires the module install.php file so the idempotent installer can apply current schema/options.
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.