Section
Introduction
In Unifize, Sections are structural elements used to group related checklist items, such as data fields or action items, into organized blocks. This enhances visual clarity, improves user experience, and allows admins to apply conditional visibility at the section level. All checklist fields—including text, rich text, picklists, uploads, linked fields, and even forms—must reside within a section.
How Sections work
A Section acts as a container for other fields. Every checklist field added must belong to a section, either directly or through a Subsection.
You can create as many sections as needed within a checklist.
Sections can be reordered via drag-and-drop.
Fields placed under a section will appear grouped in the checklist UI.
Admins can configure section-level visibility and prompt logic to guide user action.
Each section includes:
A title
Conditions for visibility and behavior
Default state (open or collapsed based on checklist status)
How Sections help you
Sections support process clarity and checklist usability by:
Structuring checklists into logical phases (e.g., "NC Details", "Impact Assessment", "Resolution Actions")
Collapsing long checklists into manageable views
Applying visibility logic to entire blocks of fields
Improving navigation and comprehension for end users
Example:
In a Nonconformance (NC) process:
Section 1: “NC Details” (basic issue info)
Section 2: “Impact Assessment” (severity and risk)
Section 3: “Corrective Actions” (linked records and forms)
Roles and permissions
Role
Permissions
Admin
Create, rename, reorder, and delete sections. Configure visibility, prompts, and conditions.
Org Member
View and interact with sections during checklist completion. Can only see sections made visible to them.
External User
View visible sections if given access to the record. Cannot interact with hidden sections or modify any content.
Section Field settings
When editing a section, admins can control which checklist status (e.g., Pending, Completed) the section opens by default in. This can be used for keeping “NC Details” section expanded during initial investigation and collapsed after completion.
Section Conditions
Setting Name
Description
Use case
Condition (Field)
Field (from checklist or form) used to evaluate the logic that affects the section.
Use “Severity” picklist to drive visibility of the “Impact Assessment” section.
Qualifier
Logical operator applied to the selected field (e.g., equals, is empty, not equal).
Show section if “Date identified” is not empty.
Behavior
Action to take when the condition is met (e.g., show section, hide section). A behavior state is only applied if the condition is met, if its not met it simply falls back to default state.
Hide “Corrective Actions” unless NC Type is “Major”.
Mandatory if not hidden
Makes all fields inside the section required only if the section is visible.
Require all fields in “NC Details” if the section is visible during Pending stage.
Last updated