Nextedy CHECKLIST provides seven workflow functions and conditions that integrate with Polarion’s workflow engine to enforce checklist completion at workflow transitions.
Blocks the transition unless all items in the specified checklists are checked.
Parameter
Required
Type
Description
checklist
Yes
String
Comma-separated list of checklist custom field IDs
Validation logic: Returns true only if every active item in every specified checklist has a checked result state (both CHECKED and CONDITIONAL states count as checked). INFORMATION-type items are excluded from validation.Multi-checklist behavior: When multiple field IDs are specified, all checklists must be fully checked (AND logic). The condition does not pass if any single checklist has unchecked items.Error message: When validation fails, the error message identifies which specific checklist has unchecked items, using the field display name.Workflow XML example:
Blocks the transition unless all mandatory items in the specified checklists are checked.
Parameter
Required
Type
Description
checklist
Yes
String
Comma-separated list of checklist custom field IDs
Validation logic: Returns true if all items flagged as mandatory are checked. Non-mandatory items are ignored. INFORMATION-type items are excluded.Workflow XML example:
If the configuration property nextedy.checklist._TYPEID._FIELDID.allMandatory=true is set, all items are treated as mandatory. In that case, ChecklistMandatoryChecked behaves identically to ChecklistAllChecked. See Configuration Properties.
Throws a user-friendly error and blocks the transition if any item in the specified checklists is unchecked.
Parameter
Required
Type
Description
checklist
Yes
String
Comma-separated list of checklist custom field IDs
Behavior: Parses each specified checklist and calls the all-checked validation. If any item is unchecked, throws an exception with a message showing the field display name.Difference from ChecklistAllChecked condition: This is a workflow function, not a condition. It executes during the transition and throws an exception to abort it, whereas conditions are evaluated before the transition starts.Workflow XML example:
Unchecks all items in the specified checklists, clearing all result states back to Empty.
Parameter
Required
Type
Description
checklist
Yes
String
Comma-separated list of checklist custom field IDs
Behavior: Parses each checklist, calls the uncheck-all operation, and stores the updated checklist back to the object. All items return to the unchecked state regardless of their previous result state. Notes and other item metadata are preserved.Use cases:
Reopening a work item that was previously completed
Resetting review cycles when a document returns to draft
ChecklistUncheckAll preserves the checklist items and only clears their result states. ChecklistResetToTemplate discards all items (including manually added ones) and replaces them with the template. Choose based on whether you need to keep custom items.
Resets the specified checklists to their configured template state, discarding all user changes.
Parameter
Required
Type
Description
checklist
Yes
String
Comma-separated list of checklist custom field IDs
skipForUsers
No
String
Comma-separated list of user IDs who bypass the reset operation
Behavior: For each specified checklist field, calls the reset operation which clears all checklist data and re-applies the configured template. All user modifications — checked states, notes, manually added items — are discarded.Workflow XML example:
The skipForUsers parameter allows specific users to trigger workflow transitions without the reset executing. Use this during data migration or bulk operations where administrators need to move work items through workflows without resetting their checklists. Remove the bypass after migration is complete.
Applies the configured checklist template to the specified checklists, merging template items into existing data.
Parameter
Required
Type
Description
checklist
Yes
String
Comma-separated list of checklist custom field IDs
Behavior: For each specified field, applies the template configured via workItemTemplateId (or documentTemplateId for documents). Template items are merged into the existing checklist, adding any missing template items without removing user-added items.Workflow XML example:
This ensures the checklist contains the latest template items before transitioning to a status where template merging is disabled. See Freezing Checklists by Status.
ChecklistApplyTemplatemerges template items into the existing checklist, preserving user modifications and manually added items. ChecklistResetToTemplatereplaces the entire checklist with the template, discarding all user changes.
There are no built-in workflow conditions for rejected (NOK) items. To create workflow logic based on rejected item counts, use the IChecklistService API to implement custom workflow conditions. See IChecklistService API for details.
Configuration Properties — Complete reference for all nextedy.checklist.* properties including template IDs, merge control, mandatory flags, and icon customization
IChecklistService API — Programmatic access to parse, store, and reset checklists for custom workflow conditions and scripted automation
Workflow Gates and Validation — Step-by-step guide for adding checklist conditions and functions to Polarion workflow transitions
Freezing Checklists by Status — Configure status-based template merge control to freeze checklists at approval or review milestones