> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Icon, Feature-Toggle, and Baseline Properties

> Reference for configuration properties that control checklist item **icons**, product **feature toggles**, general behavior flags, and **baseline** history lookup.

export const LastReviewed = ({date}) => {
  if (!date) return null;
  const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
    year: "numeric",
    month: "long",
    day: "numeric",
    timeZone: "UTC"
  });
  return <p className="mt-10 text-sm text-gray-400 dark:text-zinc-500 not-prose">
      Last reviewed on {formatted}
    </p>;
};

Reference for configuration properties that control checklist item **icons**, product **feature toggles**, general behavior flags, and **baseline** history lookup.

All properties are set in **Administration > Configuration Properties** using the `nextedy.checklist.*` namespace.

## Icon (Result-State) Properties

Each result state's icon is rendered using a Font Awesome CSS class. These properties override the default icon class per state.

| Name                                 | Type                      | Default               | Description                                                                                                                    |
| ------------------------------------ | ------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| `nextedy.checklist.checked_sign`     | `string` (CSS/icon class) | `far fa-check-square` | Icon class used to render the `Checked` result state icon.                                                                     |
| `nextedy.checklist.unchecked_sign`   | `string` (CSS/icon class) | `far fa-minus-square` | Icon class used to render the unchecked-state icon.                                                                            |
| `nextedy.checklist.no_sign`          | `string` (CSS/icon class) | `far fa-square`       | Icon class used to render the `Empty` (None) result-state icon.                                                                |
| `nextedy.checklist.conditional_sign` | `string` (CSS/icon class) | `far fa-plus-square`  | Icon class used to render the Conditional result-state icon. Only meaningful when `conditional_enabled` (see below) is `true`. |

```text theme={null}
# Example: override the checked icon with a custom Font Awesome class
nextedy.checklist.checked_sign=fas fa-check-double
```

<Tip>
  **Font Awesome classes**

  Values are raw CSS class strings passed straight through to the rendered icon element. Use valid Font Awesome class names available in your Polarion installation's bundled icon set.
</Tip>

## Feature-Toggle Properties

| Name                                    | Type      | Default | Description                                                                                                                                                                               |
| --------------------------------------- | --------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `nextedy.checklist.conditional_enabled` | `boolean` | `false` | Master toggle controlling whether the Conditional result state is available to users at all. When `false`, the Conditional state and its icon (`conditional_sign`) are not offered.       |
| `nextedy.checklist.debug`               | `boolean` | `false` | Enables debug mode/logging for the checklist plugin. Intended for admin/support troubleshooting use, not general operation.                                                               |
| `nextedy.checklist.searchAttempts`      | `integer` | `30`    | Number of attempts the plugin makes when searching for a related object (for example, locating a linked work item or document). Tune for performance/retry behavior in search operations. |

```text theme={null}
# Enable the Conditional result state
nextedy.checklist.conditional_enabled=true

# Increase search retry attempts (default 30)
nextedy.checklist.searchAttempts=50
```

<Warning>
  **Conditional state depends on the toggle**

  The `conditional_sign` icon property has no visible effect unless `nextedy.checklist.conditional_enabled=true` is also set. Configure both together.
</Warning>

## General Behavior Properties

| Name                                                | Type      | Default | Description                                                                                                                                                                                                                                                                                                      |
| --------------------------------------------------- | --------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `nextedy.checklist._TYPEID_._FIELDID_.allMandatory` | `boolean` | `false` | Shortcut flag that treats every item in a checklist template as mandatory by default, without marking each item individually. Follows the same type/field precedence pattern as other hierarchical properties — see [Template Configuration Properties](/checklist/reference/configuration/template-properties). |

## Baseline Configuration Properties

Baseline properties control which work item type and custom field represent a **baseline** record — a frozen checklist snapshot — used to build the queries behind the baseline history feature.

| Name                                        | Type                         | Default    | Description                                                                          |
| ------------------------------------------- | ---------------------------- | ---------- | ------------------------------------------------------------------------------------ |
| `nextedy.checklist.baselines.itemType`      | `string` (work item type ID) | `btask`    | Work item type used to represent a baseline record for checklist history.            |
| `nextedy.checklist.baselines.baselineField` | `string` (custom field ID)   | `baseline` | Custom field on the baseline item type that stores the baseline/revision identifier. |

```text theme={null}
# Use a custom work item type and field to store baseline snapshots
nextedy.checklist.baselines.itemType=chlBaseline
nextedy.checklist.baselines.baselineField=revisionId
```

These two properties are read together whenever the baseline/history feature builds a Lucene query to:

* find the baseline item matching a specific revision for the current document, or
* find all baseline items (any revision) associated with the current document.

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/892YPUCat-q05Sxp/checklist/diagrams/reference/configuration/appearance-and-feature-properties/diagram-1.svg?fit=max&auto=format&n=892YPUCat-q05Sxp&q=85&s=5d417f3d3d96c08e2d80f370d05c68b2" alt="Baseline lookup flow: a document requests baseline history, config is read for the item type and baseline field, then a Lucene query is built to find either the specific-revision baseline item or all baseline items for any revision" style={{ maxWidth: "720px", width: "100%" }} width="680" height="420" data-path="checklist/diagrams/reference/configuration/appearance-and-feature-properties/diagram-1.svg" />
</Frame>

<Note>
  **Result state counting in baselines and summaries**

  The Checklist summary field currently counts "not ok" (rejected/red) items together with unchecked/empty items — there is no separate count for "not ok" versus "unchecked/empty" in the summary. See [Summary Field Reference](/checklist/reference/summary-field) for the full counting model. There is also no predefined workflow function to verify that all checklist items are answered as either ok or not-ok; this requires a custom scripted condition built against the checklist API. Treat this as a known limitation when designing baseline-driven audit or compliance comparisons.
</Note>

## Related Configuration

* [Template Configuration Properties](/checklist/reference/configuration/template-properties) — properties that resolve which checklist content is treated as the template.
* [Permission, Freeze, and Read-Only Properties](/checklist/reference/configuration/permission-and-freeze-properties) — properties controlling who can edit checklist structure and results.
* [Property Hierarchy and Precedence Reference](/checklist/reference/configuration/property-hierarchy-reference) — the general 4-level precedence model shared across hierarchical properties like `allMandatory`.
* [Summary Field Reference](/checklist/reference/summary-field) — how checked, rejected, and mandatory counts are aggregated for reporting.

<Accordion title="Sources">
  **KB Articles**

  * Checklist configuration properties

  **Source Code**

  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/ChecklistConf.java`
  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/ChecklistAdminServlet.java`
  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/ChecklistSettings.java`
  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/internal/ChecklistSetupService.java`
  * `proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/ChecklistItem.java`
</Accordion>

<LastReviewed date="2026-08-31" />