Understand server-side numeric validation | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/visitor-intelligence-live-engagement-server-validation Publisher: Pixie Technologies LLC Settings, privacy and retention Understand server-side numeric validation Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. The controller enforces a minimum of 1; the form supplies the practical upper limits. Audience: CRM administrators, authorised service and sales staff, privacy teams and website implementers; Permission: Visitor Intelligence: Manage Settings; Module v1.4.0; Where to goAdmin Area → Visitor Intelligence → Settings Before you start - Verify the module is active and use the exact navigation shown above. - Use an account with the stated module and core CRM permissions. - Use known test records when changing statuses, visibility, saved filters or global navigation. What this guide helps you do The controller enforces a minimum of 1; the form supplies the practical upper limits. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Admin Area → Visitor Intelligence → Settings. - Select the record or action required for understand server-side numeric validation. - Complete the displayed fields and choices described in this guide. - Save, submit, approve or confirm the action as shown on screen. - Refresh the relevant list, record or report and verify the expected result. Fields and options WorkspaceAdmin Area → Visitor Intelligence → Settings ActionThe controller enforces a minimum of 1; the form supplies the practical upper limits. Rules and limits - Only controls rendered by the supplied module are documented; hidden AJAX helpers are mapped to their visible parent workflow. - Core CRM record permissions and module permissions are both enforced where the code checks them. Check it worked - The understand server-side numeric validation action completes without a validation or permission error. - The affected record, stock balance, response, session or style reflects the saved state. - Audit, notification, report or portal evidence appears only where the module code creates it. Security, privacy and operational checks - Use a controlled test record before applying changes to live inventory, recipients, visitor tracking or global styling. - Grant only the minimum module and core CRM capabilities needed for the task. Related guides Understand the full-IP fallback (https://pixiecrm.com/help-centre/visitor-intelligence-live-engagement-model-fallback)Save Visitor Intelligence settings (https://pixiecrm.com/help-centre/visitor-intelligence-live-engagement-save-settings)Settings, privacy and retention (https://pixiecrm.com/help-centre/topic/visitor-intelligence-settings-privacy-retention)Browse all Visitor Intelligence & Live Engagement guides (https://pixiecrm.com/help-centre/category/visitor-intelligence-live-engagement)Leads and pipeline (https://pixiecrm.com/help-centre/category/leads-pipeline)Customers and contacts (https://pixiecrm.com/help-centre/category/customers-contacts)Communications (https://pixiecrm.com/help-centre/category/email-communications)Data, privacy and security (https://pixiecrm.com/help-centre/category/data-privacy-security)Enterprise integrations (https://pixiecrm.com/help-centre/category/enterprise-integrations)Advanced Task Filters (https://pixiecrm.com/help-centre/category/advanced-task-filters)