Track and Compare Checklist Baselines

​

What a baseline captures

• an ID (the revision/baseline value)
• a label (typically the ID combined with the baseline work item’s title)
• the creation date of the baseline work item
• the workflow status of the baseline work item
• a URL linking to the document at that specific revision

1

Confirm the baseline item type and field

Baseline tracking is configured per document and looks for baseline records using two configuration properties:

# Work item type that represents a "baseline" record for checklist history
nextedy.checklist.baselines.itemType=btask

# Custom field on the baseline item type that stores the baseline/revision identifier
nextedy.checklist.baselines.baselineField=baseline

Both properties have defaults:

Configuration property	Default	Purpose
nextedy.checklist.baselines.itemType	btask	The work item type queried as a baseline record
nextedy.checklist.baselines.baselineField	baseline	The custom field on that type holding the revision identifier

If your project already uses btask for something unrelated to baselines, override nextedy.checklist.baselines.itemType in Administration > Configuration Properties to point at a dedicated work item type instead.

Baseline work items must actually exist and be linked to the documentThe baselines list is built entirely from work items matching the configured type and field — it does not automatically snapshot a document’s checklist state on its own. If no work item of the configured type (with the baseline field populated) exists for a given revision, that revision will not appear in the baselines list, even if the document itself was revised.

2

Understand the two rendering modes

The baselines feature renders in one of two ways, depending on whether a specific revision is in context:

• General listing — queries all work items matching the configured baseline item type and sorts them by the baseline field, producing the list of baseline entries (ID, label, date, status, URL).
• Revision-scoped rendering — when a specific revision is active in the viewing context, the widget instead looks up the one baseline work item matching that revision and renders the checklist as it existed at that baseline.

3

Place the baselines view on the document

The baselines list is rendered as part of a document’s (LiveDoc) checklist tooling, alongside the checklist itself. Because a document can have multiple checklists, the baselines view needs to know which checklist it should reflect.At minimum, confirm the following are set for your document:

• the target document the baselines view is bound to
• the checklist ID within that document, required when the document defines more than one checklist
• an optional title to display above the baselines list

Verify in applicationThis documentation set does not give the exact Velocity/report-page syntax for embedding the baselines widget on a document page — only the equivalent test run checklist embedding syntax. Check your document’s report/page configuration in the application, or consult Set Up a Document (LiveDoc) Checklist, for the precise embedding steps.

4

Exclude the baselines view from PDF export (if needed)

The baselines view supports a flag to hide it when the document is exported or rendered as PDF.

hideInPdf may not currently suppress renderingA flag to hide the baselines view in PDF output exists, but its effect on the exported output is unconfirmed. Verify actual PDF output in your environment before relying on it to keep baselines out of exported documents.

5

Review baseline status and navigate to a revision

Each entry in the baselines list shows:

• the baseline label (falls back to just the ID if the baseline work item has no distinct title)
• the date the baseline work item was created
• the status of the baseline work item (its workflow status, shown as an icon/label)
• a URL linking directly to the document at that revision

Clicking a baseline’s URL navigates to the document as of that revision, where the checklist form extension renders the checklist items with the result states (Empty, OK, NOK, Pending) as they were recorded at that point in time.

Use baselines with restricted checklist permissions for audit trailsNextedy CHECKLIST does not currently track which user checked or commented on an individual checklist item, or when they did so, as a built-in, per-item audit feature. If your audit or compliance process needs that level of attribution, combine baseline tracking with the adminPermission configuration property (see Control Who Can Change the Checklist) to split a single checklist into team-specific checklists, each restricted to the users responsible for that portion — the baseline snapshot then shows what was completed at each freeze point, while permissions constrain who could have completed it.

​

Comparing baselines for compliance review

1. Open the document’s baselines list to see every recorded revision, its date, and its workflow status.
2. Select an earlier baseline to view the checklist exactly as it stood at that revision (result states for every checklist item, including any mandatory items).
3. Select a later baseline (or the current document state) and compare which items changed result state between the two points.
4. Cross-reference the workflow status shown on each baseline entry to confirm the checklist was in the expected state (e.g. all mandatory items checked) before the document transitioned to that status.

​

You should now see

​

See also

• Control Who Can Change the Checklist
• Set Up a Document (LiveDoc) Checklist
• Configure Gate Enforcement (DoD / DoR) and Freeze on Status
• Export Checklists and Surface Progress in Reports