Column Features
Can I rename the first column in RISKSHEET?
No, the first column (work item identifier/name) is a system-controlled column that cannot be renamed. This column is fixed to maintain consistency with Polarion’s work item structure. You can customize other aspects like visibility, ordering, and calculated columns. See Column Configuration for supported customization options.Can I edit rich text fields directly in RISKSHEET?
RISKSHEET has limited support for editing rich text fields. When you edit rich text fields inline, formatting (especially line breaks) may be lost because RISKSHEET converts rich text to plain text for grid display. For rich text editing, use Polarion’s native interface or configure columns as plain text type. See Work with Rich Text Fields and Rich Text Formatting Loss.Can I save my own personal column views?
Currently, only administrators can create saved views, which are then shared with all users. Individual users can temporarily hide/show columns using the “Select visible columns” feature, but these preferences are not saved between sessions. For frequently used column configurations, request your administrator to create saved views. See Create Saved Views and Control Column Visibility.Can I make dropdown values dependent on other fields?
Dependent enums (cascading dropdowns) are not currently supported in RISKSHEET. As a workaround, you can use separate enum columns and document the expected relationships, or use formula columns to validate combinations. This feature is planned for future releases. See Configure Enum Columns for current enum capabilities.Can formulas populate dropdown values dynamically?
Formula-based dropdown population is not currently supported. Formulas can calculate values and perform logic, but cannot dynamically generate enum option lists. Dropdown values must be predefined in Polarion’s enumeration configuration. See Configure Calculated Columns for supported formula features.Work Item and Document Features
Can RISKSHEET aggregate work items from multiple documents?
No, RISKSHEET follows a 1:1 relationship model where each RISKSHEET is a visual representation of a single Polarion document. RISKSHEET cannot automatically route or aggregate work items from multiple documents. For multi-document scenarios, create separate RISKSHEETs per document or consolidate work items into a single master document. See Data Model and Work Items.Can I show work items linked to upstream items?
Yes, you can display work items connected through multi-level relationships using custom data rendering. This allows you to show items linked to parent work items rather than directly linked to the current row. See Render Custom Data for examples of traversing upstream link hierarchies.Does RISKSHEET support Polarion collections?
Collection-aware filtering is planned but not yet fully implemented in RISKSHEET. Currently, use selective branching strategies to manage multiple releases or variants. If your workflow requires collection-based scoping, contact Nextedy support for workarounds and roadmap updates. See Work with Collections and Configure Variant Management.Review and Approval Features
Can I approve work items directly from RISKSHEET?
RISKSHEET can display approval status in columns, but approval actions (approving/rejecting) must be performed in Polarion’s native interface. This limitation exists because approval workflows often require electronic signatures and audit trails that are handled by Polarion. See Configure Approval-Based Reviews for current capabilities.Can I edit the Resolution field in RISKSHEET?
No, the Resolution field cannot be edited directly in RISKSHEET because it is tied to mandatory workflow transitions. As an alternative, configure the rejection workflow using therejectedResolution configuration property to automatically set resolution values during risk rejection. See Configure Remove/Delete Actions.
Can I capture signatures when rejecting risks?
RISKSHEET does not support electronic signature capture in inline editing or dialogs. For workflows requiring signatures, configure the rejection action without signature requirements in RISKSHEET, then create a separate Polarion workflow action that handles signature verification. This split-workflow pattern is recommended for compliance scenarios. See Configure Remove/Delete Actions.Feature Comparison
| Feature | Supported | Workaround Available | Planned |
|---|---|---|---|
| Personal saved views | No | Use admin-created views | Yes |
| Dependent enums | No | Use separate enums + validation | Yes |
| Formula-driven dropdowns | No | Use static enums | Yes |
| Collection filtering | ⚠️ Partial | Use branching | Yes |
| Inline approvals | No | Display status only | Yes |
| Rich text editing | ⚠️ Limited | Use Polarion UI | ℹ️ Under review |
| Multi-document aggregation | No | Separate RISKSHEETs | Not planned |
Related Topics
- Configuration Questions - Setup and customization help
- Column Configuration Guides - Complete column setup instructions
- Troubleshooting FAQ - Common issues and solutions
- Changelog - Feature release history