Text
Last updated
Last updated
The Text Field is one of the most commonly used checklist field types in Unifize. It allows users to enter plain, multiline text responses directly within a record. Ideal for capturing short descriptions, justifications, names, or open-ended comments, the Text Field supports configurable behavior based on record status or conditions.
This field is best used where structured formatting is not required, but freeform input is necessary for documentation, decision-making, or workflow tracking.
A Text Field appears directly in the checklist with a basic text input box. Admins can choose whether it accepts a single line of input or supports Multiline input (i.e., larger free-text boxes).
Unlike Rich Text fields, Text Fields do not support formatting (like bold or bullets), but they are simpler and quicker for users to fill out. These fields are compatible with condition-based visibility, default values, and checklist automations.
Text Fields provide a lightweight way to collect and store user input across processes. They’re ideal when you don’t need formatting but want structured data entry.
Action item descriptions
Quick user comments or summaries
NC titles or root cause statements
Deviation identifiers or tags
Simple one-line responses
Easy to configure and complete
Supports default values and placeholders
Can be made mandatory or conditionally visible
Suitable for both brief and moderately detailed input
Faster to use than formatted fields
Role
Capabilities in Text Fields
Admin
- Configure text field settings- Set conditions, default values, layout, and visibility
Org Member
- Enter/edit content in the checklist section of a process
External Member
- Can enter/edit content only if the field is made accessible by admin-defined conditions
Access and editability depend on checklist logic set by the admin (e.g., based on role, status, or other fields).
Text Fields provide simple configuration options via the Text Field Settings tab. Admins can define:
Placeholder: Optional text shown before entry (e.g., “Describe the issue”)
Multiline (checkbox): Enable for larger input areas where more content is expected
Default Value: Prefill the field with a standard entry (can be edited by users)
Suppress notifications for default values: Prevents notification triggers from firing when only the default value is saved
These settings make it easier for users to understand what’s expected and ensure smoother form completion.
Like other checklist fields, Text Fields support condition-based logic for visibility, editability, and mandatory rules. Admins can define logic from the Conditions tab.
Setting
Description
Use Case (Industry Context)
Show until condition met
Field is visible by default and hidden when the condition is true
Show “Action Description” until “Status” = Closed (CAPA execution)
Hidden until condition met
Field remains hidden until the specified condition is met
Display “Justification” only when “Exception Flag” = Yes (Deviation handling)
Mandatory until condition met
Field is required until a condition is satisfied
Make “Root Cause” mandatory until “Escalated” = No (Quality investigations)
Disable until condition met
Field is locked until the defined condition is true
Lock “Resolution Summary” until “CAPA Approved” = Yes (Corrective action lifecycle)
Condition
Select a source field (checklist/form) and define a value-based condition
Trigger logic based on “Category”, “Severity”, or “Status” fields
+ Add condition (AND)
Add multiple conditions that must all be satisfied together
Make field visible only if both “CAPA Required” = Yes AND “Risk Level” = High
Behavior
Override default behavior manually (Show/Hide/Disable)
Use to enforce or test field behavior irrespective of logic rules
Mandatory if not hidden
Field becomes required only if it is visible
Ensure “Explanation” is filled out when shown due to upstream field logic
