Column Definition Properties
Core Properties
Binding Patterns
Task link columns and their nested task attribute columns use three binding patterns:Link Field Convention
Every task link column has an associated link field identified by appending_link to the binding name. This _link suffix field stores the hyperlink URL to the linked work item:
When a new task is created, Nextedy RISKSHEET automatically sets both the
taskColumn value and the taskColumn_link field to maintain synchronized references.
Task Data Type Configuration
Task link columns depend on thedataTypes.task configuration in the sheet configuration. This section defines the work item type, link role, display name, navigation behavior, document scope, and filtering for all task-related operations.
Core Task Properties
Two-Level canCreate Control
canCreate operates at two independent levels and both must permit creation for users to add new items inline:
A common regulated-industry pattern combines both:
dataTypes.task.canCreate: false together with per-column canCreate: false on link columns forces users to pick tasks from a curated library rather than create new ones inline.
Task Creation Target Document
Single vs. Multi-Project Configuration
Subsheet Navigation Pattern
WhendataTypes.task.linkToRisksheet: true is combined with dataTypes.task.document, the task link column’s cell becomes a clickable hyperlink that opens the referenced child risksheet document. This enables hierarchical risksheet architectures, for example:
- Master risksheet lists hazards with a task link column (e.g., RC ID).
- Child risksheets hold the detailed mitigation analysis for each hazard.
- Clicking the cell opens the matching child risksheet.
Reverse-Direction Linking
Task Column Identification
The grid identifies which column holds the task identifier through thetaskColumn property in grid settings:
This property is essential for all task management operations. Without it, add task, remove task, and task autocomplete functions will not work.
Task Creation Behavior
When you create a new task (via context menu or toolbar), Risksheet follows one of two paths depending on whether the risk item already has tasks:First Task on a Risk Item
- A unique task ID is generated automatically using the ID generator.
- The task ID is stored in the
taskColumnfield. - The corresponding
_linkfield is populated with the work item reference. - The cursor focuses on the
zoomColumn(if configured) for immediate editing. - The operation is recorded for undo support.
Additional Tasks on a Risk Item
- The current row record is cloned.
- Task-level fields are cleaned (task ID, link fields, readonly flags, and all task attribute columns).
- Multi-enum columns are initialized to empty arrays to prevent undefined values.
- A unique task ID is generated for the new task.
- The new row is inserted immediately after all existing sibling tasks (rows sharing the same
systemItemId). - The operation is recorded for undo support.
Task Removal Behavior
Task removal operates with context-aware logic based on whether the risk item has single or multiple tasks:Single Task Removal
When the risk item has only one task, removing it clears all task-related fields from the work item record rather than deleting the entire row. The risk item row is preserved. Fields cleared include:- Task column value and its
_linkfield - All task attribute fields on the row
- Task-level link references
Multi-Task Removal
When the risk item has multiple tasks (detected by checking if adjacent rows share the samesystemItemId), removing a task deletes the entire row from the grid. The row ID is marked with a ;* suffix before deletion for processing during save.
Permission Checks
Task removal validates permissions before executing:
All task removal operations are fully undoable.
Autocomplete and Search
Task link columns provide autocomplete functionality for linking existing tasks:Nested Task Columns
Task link columns typically have nested sub-columns that display properties of the linked task. Nested task attribute columns use thelinkedItem.fieldId binding pattern (e.g., bindings: task.title) to surface fields from the linked task work item. These columns are automatically cleared when creating new tasks and are subject to task-level readonly permissions (systemTaskReadOnly and systemTaskReadOnlyFields).
Readonly Protection
Task link columns respect multiple layers of readonly protection:Context Menu Actions
Right-clicking a task link cell provides task-specific menu options:Export Behavior
Excel Export
Task link columns export as plain text, with HTML link markup stripped to produce clean text values. Multi-task rows are exported as separate rows in the Excel output.PDF Export
Task link columns render in PDF using therenderDataCell function, which resolves the link label property for display. Use exportSubTable or exportDownstreamTable to export task data as separate tables in the PDF output.
Complete Example
mitigationAction work items linked via the mitigates role, scoped to the Risks/Mitigation Plan document (v24.8.1+).
Internal Properties
The following flags are managed automatically by the grid engine when a column is configured as a task link or task attribute. They are NOT user-configurable in the sheet configuration:
Do not set these flags directly — configure
type: taskLink and use the linkedItem.fieldId binding pattern instead.
Related Pages
- Item Link Columns for upstream traceability columns linking to requirements and hazards
- Multi-Item Link Columns for columns displaying multiple linked items per cell
- Column Type Reference for the complete list of column types
- Data Types for the full
dataTypesconfiguration reference - Levels Configuration for hierarchical level settings that interact with task columns