Date

1. Introduction

The Date Field in Unifize allows users to select and input calendar dates directly within a checklist. It's ideal for capturing key dates such as due dates, assessment dates, implementation timelines, or review milestones within any record-based process.

With support for conditional logic, default display behavior, and prompts, the Date Field ensures that critical time-based information is consistently and accurately collected across workflows like CAPAs, validations, audits, and more.

2. How the Date Field works

When configured, the Date Field appears as a simple date selector inside the checklist. End users:

• Click the date input box to trigger a calendar pop-up.

• Select the appropriate date using the calendar interface.

• Click “Done” to confirm the selected date.

• Can clear or edit the field if it is not locked or read-only.

• The calendar view auto-adjusts for month/year and includes quick access to Today and Clear options for usability.

---

3. How the Date Field helps you

The Date Field ensures consistency, accountability, and automation based on time-sensitive events. Unlike free-text fields, it enforces proper date formatting and integrates cleanly with workflow deadlines and status transitions.

Examples of use cases:

• CAPA due dates

• Assessment completion dates

• Planned vs actual implementation dates

• Audit scheduling

• Validation protocol timelines

Benefits:

• Guarantees consistent date format and data quality

• Enables date-based workflow automation and reports

• Prevents user error from free-text date entry

• Supports deadline tracking and visibility

• Makes checklists more structured and process-driven

---

4. Roles and permissions

Role	Permissions
Admin	- Configure field name, layout, visibility, and logic- Apply conditions and prompts
Org Member	- Select or edit dates within the field if it is editable
External Member	- Can select/edit dates only if the field is made visible/editable via admin-defined logic

Field accessibility is governed by checklist conditions and user permissions defined during setup.

---

5. Date Field settings

In the Date Field Settings tab, admins can define the following:

• Field label: Name of the date field visible to end users (e.g., “Assessment Date”)

• Placeholder: Shown when no date is selected (e.g., “Add date”)

From the Prompts and Layout tabs, you can configure:

• Column Width: Full width or half-width based on checklist layout

• Visibility Behavior: Choose if the field starts collapsed or expanded

---

6. Date Field Conditions

The Conditions tab allows admins to control when the date field appears, is required, or becomes editable. These behaviors help tailor visibility based on checklist logic.

Setting	Description	Use Case (Industry Context)
Show until condition met	Field is visible by default and hidden when the condition is true	Show “Assessment Date” until “Status” = Finalized (Audit scheduling)
Hidden until condition met	Field remains hidden until the specified condition is met	Display “Review Date” only when “Type” = Internal Audit (Quality compliance)
Mandatory until condition met	Field is required until a condition is satisfied	Require “Implementation Date” until CAPA is completed (CAPA lifecycle control)
Disable until condition met	Field is locked until the defined condition is true	Lock “Closure Date” until “Status” = Closed (Investigation workflow)
Condition	Choose a field (from form or checklist data) and define its expected value	Tie visibility of date fields to record type or decision flag
+ Add condition (AND)	Combine multiple conditions for complex logic	Show only if “CAPA Required” = Yes and “Severity” = Critical
Behavior	Manually override visibility: Show, Hide, or Lock	Force the field to stay hidden for pilot groups
Mandatory if not hidden	Field becomes required only when it’s visible	Ensure “Target Date” is filled if field appears due to escalation conditions

🖊️Edit this page