# Universal Checklist settings ### **Universal Checklist settings** Unifize checklists offer powerful customization through Universal checklist field settings, a set of configuration options available across all field types. These settings work alongside each field’s unique properties (like picklist options, text formatting, date restrictions, etc.) to define how fields behave, display, and interact within a checklist. While each field type (e.g., Picklist, Text, Date) has its own specialized settings, the universal settings apply consistently across them all and include: * **Conditions**: Set visibility, requirement, or interactivity rules based on other fields. * **Prompts**: Notify or nudge specific users or roles to complete the field. * **Layout**: Control the field’s visual arrangement and width in the checklist. ### Conditions | **Setting category** | **Setting name** | **Description** | **Use case** | | ----------------------------- | --------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | **Top-level condition modes** | **Show until condition met** | Field is visible by default, hides when the condition is true | Temporarily display fields that are no longer relevant once a certain value is selected | | | **Hidden until condition met** | Field stays hidden until a condition is satisfied | Show dependent fields based on user input (e.g., show "Reason" when "Status" is "Rejected") | | | **Mandatory until condition met** | Field is required unless the condition becomes true | Make a justification field mandatory unless a bypass condition is selected | | | **Disable until condition met** | Field is locked (read-only) until a condition is satisfied | Prevent edits unless a prerequisite step is completed | | **Condition logic** | **Condition (Field)** | Checklist or form field used to trigger the logic | Picklist, checkbox, or user fields used to determine logic | | | **Qualifier (Value)** | The specific value that triggers the logic | e.g., “Yes”, “Red”, “John Doe” | | | **+ Add condition (AND)** | Adds a second condition that must also be true | e.g., Show field only if Status = “Open” AND Priority = “High” | | | **Mandatory if not hidden** | Makes field required if it is visible due to logic | Use when conditional fields must be completed once shown | | **Behavior actions** | **Hide field** | Hides the target field entirely | Use to simplify checklists and avoid irrelevant fields | | | **Disable/Lock field** | Field is visible but disabled (read-only) | Prevent further edits after a specific step or selection | | | **Show field** | Makes a hidden field visible when the condition is met | Used to progressively reveal fields as needed | | | **Dependent picklist include** | Filters picklist values to only include matching ones | Cascading picklists (e.g., State based on Country) | | | **Dependent picklist exclude** | Filters picklist values to exclude matching ones | Hide invalid options based on prior selections | ### **Prompts** | **Setting Category** | **Setting Name** | **Description** | **Use Case** | | -------------------- | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | **Prompt recipient** | **Search People / Roles** | Defines who will be prompted. You can choose specific users or dynamic roles like Creator, Participant, or Owner. | Prompt checklist owners to complete fields relevant to their step. | | | **Individual Users** | Allows you to manually select specific users in your org to receive the prompt. | Use for special approvals, SME involvement, or ad hoc reminders. | | | **Roles (e.g., Owner, Participant, Creator)** | Prompts users dynamically based on their assigned role in the conversation. | Ensures prompts stay relevant even if people change across records. | | **Trigger timing** | **Every time they view the conversation** | Prompts are shown persistently each time the user opens the record. | Reinforce urgency or mandatory actions during ongoing work. | | | **When they get added to the conversation** | Triggered once when the user is newly added as a participant. | Good for onboarding contributors to a record who must take specific actions. | | | **When they close the conversation** | Prompts appear just before a user closes the record’s conversation. | Prevents users from leaving incomplete required data before closure. | | | **When the previous step is completed** | Triggers the prompt once the previous checklist step is marked complete. | Ensures sequential task ownership—next person is nudged right on time. | ### Layout | **Setting category** | **Setting Name** | **Description** | **Use Case** | | -------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | **2D auto layout** | **1x / 2x / 3x / Max Width** | Defines the field’s width in the checklist layout grid. Smaller widths allow more fields per row. | Use 1x for compact fields like picklists or checkboxes; Max Width for rich-text or long inputs. | | | **1x (Default)** | Standard width for most fields. | Recommended for single-value inputs (picklists, numbers). | | | **2x / 3x** | Increases field width to span 2 or 3 columns. | Use for fields with slightly longer labels or expected input length. | | | **Max Width** | Field spans the full width of the checklist area. | Ideal for long text fields, file uploads, or detailed forms. | | **Row placement** | **Force start on a new row** | Ensures the field begins on its own line, regardless of available space. | Use when visual clarity or separation from other fields is needed. | [🖋️Edit this page](https://www.notion.so/VER-1-Universal-Checklist-settings-1fa860e6b45e80eba31ec9c509a5b40f?pvs=4) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.unifize.com/manage/processes/checklist/universal-checklist-settings.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.