Skip to main content
diagram

Column Definition Properties

Core Properties

Binding Patterns

Task link columns and their nested task attribute columns use three binding patterns: 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 the dataTypes.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

Having a Task project column visible in the Risksheet configuration can cause duplication errors when copy-pasting existing tasks between rows (Ctrl+C / Ctrl+V). The workaround is to remove the Task project column from the configuration. For single-project task configurations, use project (singular) instead of projects (plural) in the dataTypes section.

Subsheet Navigation Pattern

When dataTypes.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 the taskColumn 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

  1. A unique task ID is generated automatically using the ID generator.
  2. The task ID is stored in the taskColumn field.
  3. The corresponding _link field is populated with the work item reference.
  4. The cursor focuses on the zoomColumn (if configured) for immediate editing.
  5. The operation is recorded for undo support.

Additional Tasks on a Risk Item

  1. The current row record is cloned.
  2. Task-level fields are cleaned (task ID, link fields, readonly flags, and all task attribute columns).
  3. Multi-enum columns are initialized to empty arrays to prevent undefined values.
  4. A unique task ID is generated for the new task.
  5. The new row is inserted immediately after all existing sibling tasks (rows sharing the same systemItemId).
  6. The operation is recorded for undo support.
diagram

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 _link field
  • 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 same systemItemId), 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. 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 the linkedItem.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 the renderDataCell 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

This configuration creates a task link column for mitigation actions with three nested columns showing the task title, status, and assignee read from the linked task. New tasks are created as 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.
Last modified on July 10, 2026