# Number ### **1. Introduction** The **Number Field** in Unifize is designed to capture numeric input within a checklist. Whether you're logging quantities, counts, or tolerance ranges, the field makes sure that only numeric values are entered. It supports configuration for min/max limits, decimal handling, default values, and conditional visibility, which makes it ideal for quality control, validation metrics, and audit entries.
*** ### **2. How the Number field works** When configured in a checklist, the Number Field appears as a numeric input box with “+” and “–” controls and a **Done** button for the end user. * Users can manually enter values or increment/decrement using the **+/- buttons**. * The field accepts min and max values to be set and allows decimals and supports precision formatting through rounding rules. * Once the number is entered, users must click **Done** to save the input. * Every time a user saves a number, that number will show in the conversation window of the My Inbox section for that particular process. If the existing number is removed or edited, the same update will also be reflected in the conversation window as a notification. *** ### **3. How the Number field helps you** This field ensures that numeric values entered are valid, constrained, and consistently formatted, which removes ambiguity and minimizes manual correction. #### **Examples of use cases:** * Recording quantity used in a batch * Entering defect counts during inspection * Logging equipment calibration values * Capturing pass/fail thresholds #### **Benefits:** * Prevents non-numeric or invalid entries * Enforces required decimal precision and rounding * Supports numerical validation directly in the form * Improves data quality and simplifies downstream reporting *** ### **4. Roles and permissions** | **Role** | **Capabilities in Number Fields** | | ------------------- | --------------------------------------------------------------------------------------------------- | | **Admin** | Configure field settings (min, max, step, rounding), visibility, layout, and conditions | | **Org Member** | Can enter or adjust numeric values if the field is visible and editable | | **External Member** | Can interact with the Number Field only if it is made visible/editable based on admin-defined logic | **Note:** Conditional rules and field permissions may lock or hide the field depending on the user's role or record status. *** ### **5. Number field settings** #### **a. Basic settings** | **Setting** | **Description** | **Use case** | | --------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------- | | **Placeholder** | Text shown before any input is made. E.g., “Enter quantity.” | *Guide users entering batch size or defect counts in QC forms.* | | **Max** | Sets the maximum value allowed. | *Prevent input above 100% for yield efficiency in validations.* | | **Min** | Sets the minimum value allowed. | *Disallow negative input for calibration checks or units consumed.* | | **Step** | Defines the increment/decrement step size for the **+/-** buttons. | *Set increment to 0.1 for precision instruments or testing tolerances.* | Note: If a user enters a number beyond the min/max range, an error is shown: “The number must be in the range of X and Y.” *** #### **b. Trailing zeroes and rounding off** | **Setting** | **Description** | **Use case** | | ----------------------------- | ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | **Decimal places** | Defines the number of digits to show after the decimal point. | *Display 2 decimal places for chemical concentration tracking.* | | Don’t round off or truncate | All digits are stored and shown exactly as entered. | *Maintain full measurement accuracy for metrology or validation readings.* | | **Round off when displaying** | Round visually for UI display, but preserve the full number in the database. | *Show 2 decimal places on screen while storing full precision for future audits.* | *** #### **c. Default value** | **Setting** | **Description** | **Use case** | | -------------------------- | ------------------------------------------------------------------ | -------------------------------------------------------------------------- | | **Default value** | Pre-populates the number field with a starting value | *Auto-fill “0” for rejection count in defect forms.* | | **Suppress notifications** | Disables notification triggers when the default value is unchanged | *Avoid email alerts when using placeholder defaults that aren’t critical.* | ### Number field conditions | **Setting** | **Description** | **Use case** | | --------------------------------- | ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | | **Show until condition met** | The number field is visible by default and becomes hidden once the condition is satisfied. | *Show “Defect Count” field only until “Status” = Resolved* (Quality/NC closure tracking) | | **Hidden until condition met** | The field is hidden by default and shown only after the condition is met. | *Reveal “Sample Size” only when “Test Required” = Yes* (Pharma/Validation protocol) | | **Mandatory until condition met** | The number field is required until a condition is met; after that it becomes optional. | *Make “Units Retested” required until “Final Outcome” = Approved* (CAPA revalidation) | | **Disable until condition met** | The number field is locked (non-editable) until the condition becomes true. | *Prevent editing “Calibration Tolerance” until “Technician Assigned” is selected* (Metrology) | | **Condition** | Allows you to specify which form/checklist field and value should drive the condition. | *Trigger logic based on “Severity”, “Deviation Type”, or “Stage” field values* | | **+ Add condition (AND)** | Enables combining multiple logic conditions to enforce complex visibility rules. | *Show “Deviation Count” only when “Area” = Manufacturing AND “Batch Type” = Production* | | **Behavior (dropdown)** | Overrides the default logic. Options include: “Hide field”, “Disable/Lock field”, “Show field”. | *Force field visibility regardless of logic when building exceptions or fallbacks* | | **Mandatory if not hidden** | Makes the number field mandatory only when it is visible (checkbox toggle). | *Ensure “Scrap Quantity” is required only when defect-related fields make it visible* | [🖊️Edit this page](https://www.notion.so/Admin-v-215860e6b45e8044b72ec902732e81f8?source=copy_link)