PROCESIO
OverviewPlatform ActionsIntegrations & DemosCustom ActionsDeveloperโ€™s Guide

Number Input

Like the Text Input, it supports regex-based validation, default values, read-only and disabled modes, and full runtime manipulation via the Procesioโ€ฆ

The Number Input element is purpose-built for capturing numeric data from users. Whether collecting quantities, prices, scores, percentages, or any other numeric value, it enforces numeric input at the browser level while remaining flexible enough to accept both integer and decimal values.

Like the Text Input, it supports regex-based validation, default values, read-only and disabled modes, and full runtime manipulation via the Procesio Forms data model. Use it wherever numeric precision matters and you want to prevent non-numeric entries without writing custom validation logic.

Key Use Cases

โ€ขย ย ย ย ย ย ย  Quantity fields, pricing inputs, age or score collection

โ€ขย ย ย ย ย ย ย  Dynamically updating a total or calculated field at runtime by setting value

โ€ขย ย ย ย ย ย ย  Setting min/max constraints via regex or external form logic

โ€ขย ย ย ย ย ย ย  Locking a numeric field after a process step by toggling readonly at runtime

โ€ขย ย ย ย ย ย ย  Pre-filling budget, quota, or threshold values from process variables on form load

Runtime API โ€” Attributes in Procesio Forms

All attributes below are accessible and modifiable at runtime via the element's data model in Procesio Forms โ€” on any available event such as onLoad, onChange, or custom triggers.

API NameDescriptionTypeDefaultNotes
labelDisplay label shown above the input fieldstringโ€”โ€”
placeholderHint text shown inside the empty fieldstringโ€”โ€”
tooltipHelp text shown alongside the labelstringโ€”โ€”
infotextSupplementary info displayed below the inputstringโ€”โ€”
defaultvalueInitial value when the form loadsnumber|stringโ€”โ€”
valueCurrent runtime value โ€” read or set programmaticallynumber|stringโ€”โ€”
readonlyIf true, users can view but not edit the valuebooleanfalseโ€”
disabledIf true, the field is fully non-interactivebooleanfalseโ€”
visibleControls element visibilitybooleantrueโ€”
nameUnique name for referencing in logic/eventsstringโ€”โ€”
idUnique element IDstringโ€”โ€”
requiredMarks the field as mandatory on submitbooleanfalseโ€”
regexRegex pattern for custom numeric validationstring|nullโ€”โ€”

For support, please join our Discord community for further assistance and support.

On this page