How to Add Inputs within an Object
Found in: Data > How to Add Inputs within an ObjectA checkpoint represents a specific quality control step during an inspection. By default, a checkpoint only captures a general outcome such as Pass or Fail. While this works for simple checks, most inspections require recording detailed and precise information—for example, product dimensions, weights, or defect observations.
This is where inputs come in. Inputs let technicians capture structured data directly within a checkpoint. Instead of relying on generic results, inputs allow each inspection step to be measurable, traceable, and tailored to the product being inspected.
Why Inputs Are Important
Precision: Capture exact values instead of just pass/fail (e.g., Length = 45 cm, Carton Barcode = 123456).
Flexibility: Customize inputs to match inspection needs, whether it’s textile measurements, carton sizes, defect counts, or batch numbers.
Data Quality: Collect structured and standardized data, making inspection results easier to review, analyze, and compare across products, batches, or factories.
Steps to Add Inputs
Step 1: Navigate to checkpoint and click on the checkpoint where you want to configure inputs.
Step 2: Click the Manage Inputs button: This opens the input management panel for the selected checkpoint.
Step 3: To add a new Input, click the + Add input button.
Step 4: A new input entry will appear in the list. Click on it
Step 5: Configure the Input:
1. Enter the Input Name: Provide a clear and descriptive name (e.g., Export Carton Barcode Scan). This helps technicians understand what data they need to enter.
2. Enter the Input Code: Leave blank to auto-generate. If you manually change this code, all existing saved data for this input will be lost.
3. Select the Input Type: Choose the type of input depending on the kind of information you want to collect.
Values options and their Use Cases are:
| Input Types | It is used for? |
|---|---|
| Text Field | Used for free-text data entry. Suitable for recording information like carton numbers, batch codes, or any value that does not need predefined options. |
| Single choice | Allows the technician to select one option from a predefined list (e.g., Yes/No, Pass/Fail). Useful for simple decisions or status checks. |
| Multiple choice | Enables selecting more than one option from a list (e.g., Defects observed: Scratch, Dent, Color Fade). Best when multiple conditions may apply simultaneously. |
| Barcode scan | Designed for scanning barcodes using the device camera. Ideal for verifying product IDs, carton labels, or serial numbers. Options include trimming leading zeros for EAN/UPC barcodes. |
| Measurements | Collects numeric values against predefined specifications and tolerances. For example, carton size: Standard = 5, Lower Tolerance = 2, Upper Tolerance = 2. Can be configured to automatically fail if values are out of tolerance. |
| 2d Table | Lets you capture structured data in a table format with rows and columns. For example, tracking Product A / Product B with columns for Details, Price, and Quantity. Very useful for multi-dimensional recording. |
| Single Choice with Score | Extends the single-choice input by assigning a numeric score to each option (e.g., 3 = OK, 4 = Good, 5 = Excellent). Helpful for quality ratings, inspections, or performance scoring. |
Click the Save this input button to save the input only, OR click the Save and close button to submit and close the modal window.
Add More Inputs (Optional). Repeat the process by clicking the + Add input button again. You can also edit any existing input by selecting its tab and modifying details.
Example Use Case
Imagine a checkpoint for inspecting textile rolls:
Input 1: “Length (cm)” - Numeric field with min/max range.
Input 2: “Color Shade” - Dropdown with predefined options.
Input 3: “Defect Notes” - Free-text field for observations.
Inputs should be designed to capture only the data that matters for evaluation. Too many unnecessary fields may slow down inspections.