All pages
Powered by GitBook
1 of 1

Loading...

Subsection

Introduction

Subsections in Unifize are collapsible, structured containers used within a Section to further organize checklist fields. They function similarly to sections but provide more granular control and layout flexibility. Admins can use subsections to group related checklist items within larger sections, set visibility logic, and prompt specific users based on workflow stages.


How Subsections work

  • A Subsection is added inside a Section and can contain various checklist field types (text, date, uploads, etc.).

  • Subsections allow you to break complex sections into smaller, more focused groups.

  • They support conditional visibility, layout control, and user prompts.

Each subsection includes:

  • A title

  • Optional prompts for user guidance

  • Conditions to control visibility and behavior

  • Layout settings to control field arrangement


Subsections help simplify complex workflows by:

  • Structuring large sections into manageable parts (e.g., input details, review, sign-off)

  • Improving visual clarity for users working with multiple checklist items

  • Enabling targeted prompts to users at the right time

In a CAPA checklist:

  • Section: Root Cause Analysis

    • Subsection 1: Data Collection

    • Subsection 2: Team Evaluation



  • In Subsections, admins can configure prompt rules to notify users (by name or role) when they need to complete a subsection. Prompts can trigger based on events like viewing the record, being added, completing a prior step, or closing the conversation.

  • You can use the 2D auto-layout to control field widths (1x to Max Width). You can also force a new row to ensure visual separation between checklist elements.


You can apply conditional logic to show, hide, or require subsections based on field values from within the checklist or form.


  • During checklist configuration, if a subsection is placed above a section without any checklist fields inside it, the subsection field won’t be visible for end users.

  • During checklist configuration, if a subsection is placed above a section with checklist fields inside it, the subsection heading won’t be visible for end users.

Reducing user error by revealing only relevant fields when needed
Subsection 3: Final Approval

Behavior

Defines what happens when condition is met (e.g., show or hide field).

Hide “Extra Info” subsection if issue type is “Minor”.

Mandatory if not hidden

Makes all fields inside the subsection required, but only if visible.

Ensure user completes fields in “Final Review” if it's shown to them.

Role

Permissions

Admin

Add, configure, reorder, and delete subsections within a section. Define conditions, layout, and prompts.

Org Member

View and complete fields inside visible subsections. Cannot modify settings or structure.

External User

View visible subsections if they have access to the record. Cannot interact with hidden ones.

Setting Name

Description

Use Case

Condition (Field)

Field used to evaluate the rule logic (from form or checklist).

Show “Investigation” subsection if NC Type = “Major”.

Qualifier

Logical condition to evaluate (e.g., equals, contains, is empty).

How Subsections help you

Example:

Roles and permissions

Subsection field settings

Subsection Condition field

Feature limitation

🖊️Edit this page

Reveal subsection if "Date Identified" is not empty.