Data collection fields
The field types below capture operator input during a run. You pick a field’s type when you add it to a step. For the steps to add and configure a field, see Manage procedure steps.Datetime
A date and time for an event, used to track when something happened in production, such as when a part entered a thermal oven.Boolean
A checkbox for a true or false response, such as a pass/fail check.String
A text field for freeform responses from the floor.String fields have no length limit and support all UTF-8 characters.
Number
A numeric value. Number fields are the only type that supports validations, which check a reading against limits automatically during the run. See Field validations.Select
A list of options where the operator picks one. To let the operator pick more than one, use Multiselect.Multiselect
A list of options where the operator can pick more than one. Use it to capture several conditions at once, such as when a part is scratched, bent, and discolored.Signoff
A role-gated digital signature. You define the role required to sign off, and ION enforces it during the run. For example, a step can require a user with the Quality Inspection role to sign off before work continues. ION records who signed off with a digital signature. Turn on Peer review required to restrict the signoff to users who have not worked on the run connected to the field. You manage which roles exist and who holds each role in Users and permissions.File
A file upload. Use it when you need one specific file, such as a CSV export from a machine. For general reference files on a step, the step attachments panel is more flexible.A File field accepts a file up to 5 GB.
Tool
Links use of a tool to the run step for traceability and containment. You can limit a Tool field to specific tool part numbers, types, and calibration status.ION User
Links an ION user to the step.ION Part
Links an ION part to the step.Required fields
Fields are optional by default. Leaving an optional field blank does not block step completion. Turn on Required to force the operator to fill in the field before completing the step. A required field can also allow a Not Applicable entry, which lets the operator confirm the field does not apply rather than leaving it blank.Field validations
Number fields support validations that check a reading against limits automatically when an operator enters a value during a run. Use them to set the conditions for a passing value. For a torque value that must fall between 5 ft-lb and 10 ft-lb, add one validation for the lower limit and one for the upper limit. To author validations on a number field:- In the Step Fields section, on a number field, click Add Validation.
- Choose the comparison operator: less than (
<), less than or equal to (≤), greater than (>), greater than or equal to (≥), equal to (=), or not equal to (≠). - Enter the value to compare against.