Deactivate QR Code Manager without deleting evidence
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Disable version 2.1.1 reversibly while preserving options, signatures, compliance records, audit events and evidence.
Where to goAdmin Area → Setup → Modules → QR Code Manager → Deactivate
Before you start
- Verify the installed module reports version 2.1.1.
- Take no uninstall action: uninstall still calls the data-removal routine.
- Use an administrator account and check that no PDF generation/signing test is in progress.
What this guide helps you do
The version 2.1.1 deactivation hook is intentionally empty. Deactivation stops the active module hooks and menus but does not delete stored QR settings, signatures, compliance records, events or evidence.
Follow these steps
- Go to Admin Area → Setup → Modules.
- Find QR Code Manager and confirm the displayed version is 2.1.1.
- Select Deactivate.
- Allow the CRM module lifecycle action to finish, then reload the Modules page.
- Verify QR Code Manager is inactive.
- Reactivate the module in a controlled test, open QR Compliance Records and verify the earlier records/events remain available.
Lifecycle choices and consequences
DeactivateReversible in version 2.1.1; preserves options, signatures, audit events and compliance evidence.
ReactivateRuns the activation installer and restores active menus/hooks against preserved data.
UninstallDestructive: calls qrcode_remove_module_data(). Use only after preserving required evidence.
VersionThis safe deactivation behaviour is specific to the supplied QR Code Manager v2.1.1 code.
Rules and limits
- qrcode_deactivate_module() contains no cleanup call and intentionally preserves tenant evidence.
- qrcode_uninstall_module() still calls qrcode_remove_module_data().
- Do not confuse Deactivate with Uninstall in change instructions or operational approvals.
Check it worked
- The module becomes inactive without deleting QR settings or compliance evidence.
- Reactivation restores the module against the preserved records.
- An explicit uninstall remains separately available and destructive.
Security, privacy and operational checks
- Preserve signed/verified evidence according to legal and organisational retention requirements.
- Restrict module lifecycle actions to authorised administrators.
- Test deactivation/reactivation in staging before a production maintenance window.
Related guides
Was this guide useful?Your response is stored only in this browser.