Core Concepts
What is Risksheet? — Overview of Risksheet as a risk analysis tool within Polarion ALM, its relationship to Powersheet, and the one-document-per-risksheet design model.
Architecture — How the server plugin, client-side grid, and Polarion data layer work together to render interactive risk tables.
Data Model and Work Items — How risk items, tasks, and upstream requirements map to Polarion work items with configurable types, fields, and link relationships. All data lives in Polarion work items; Risksheet does not maintain a separate data store. Includes how visual levels (defined by the levels array) create hierarchy through cell merging on top of the underlying work item types.
Configuration
Configuration Hierarchy — How global templates, project templates, and document-level sheet configurations inherit and override each other, and how the sheet configuration structure (columns, levels, dataTypes, formulas, styles, views) shapes the grid.
Access and Visibility
User Roles and Permissions — Administrator, editor, and reviewer roles, and how permissions control what users can see and modify.
Traceability and Workflow
Traceability and Linking — Upstream links to requirements and downstream links to mitigation tasks, including role-based filtering and cross-project linking.
Review Workflows — Comment-based, work-item-based, and approval-based review processes. Note that approval review creates approval-tagged comments but does not drive Polarion’s formal approval state transitions.
System Behavior
Working Sessions — How Risksheet maintains browser sessions, handles save and refresh against Polarion data, and manages unsaved changes and concurrent editing.
Data Synchronization — How calculated values stay in sync between client-side formulas and Polarion-stored fields, and how comparison mode diffs a risk assessment against an earlier revision.
Last modified on July 10, 2026
