Use the enforced QR size limits
Configure a QR width and height inside the 10–100 range enforced by version 2.1.1.
Exact navigationAdmin Area → Setup → Settings → General → QR Code Manager
Before you begin
- Use an account with Administrator and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What this guide covers
Configure a QR width and height inside the 10–100 range enforced by version 2.1.1. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Admin Area → Setup → Settings → General → QR Code Manager.
- Select the relevant record, filter, report, model or configuration described below.
- Use the displayed action or read the current values without altering unrelated data.
- Compare the output with the code-backed rules and expected result in this guide.
- Record or correct any mismatch before relying on the output in production.
Fields, choices and supported possibilities
Exact actionUse the enforced QR size limits
Exact navigationAdmin Area → Setup → Settings → General → QR Code Manager
Module version2.1.1
VerificationConfirm the described lifecycle, setting, PDF or compliance evidence behaviour in the same workspace.
Code-backed validations and workflow rules
- Each QR dimension is clamped to a minimum of 10 and maximum of 100.
- Out-of-range saved values render at the nearest bound.
Expected result and verification
- The supported use the enforced qr size limits flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.