Despite this page’s URL, the endpoints below are not an OData service: there is no
$filter, $select, $metadata, or any other OData query surface. They are the internal data-access layer of the Risksheet client — implementation details that may change between releases and are not a supported public API.If you need a programmatic, supported way to query or modify risk data, use Polarion’s own APIs (SOAP, REST, scripting) against the underlying work items rather than the endpoints described here. All Risksheet data is stored as standard Polarion work items, subject to Polarion authorization.Base Path
The
baseUrl, projectId, and documentId values are derived from the runtime application configuration of the current LiveDoc.
HTTP Methods
Grid Item Retrieval
Retrieves all work items displayed in the Risksheet grid for the current document.Linked Item Lookup
Used to populate autocomplete suggestions foritemLink, multiItemLink, and taskLink columns based on user input and column configuration.
For task-link columns, the
query constraint may also come from dataTypes.task.query (a Lucene query that further filters task autocomplete results, per KB #48001173767).
Work Item Creation
Creates new work items submitted from the Risksheet grid.
A single submission can create a master risk item together with linked downstream task items. The server maintains three ID maps so that links between newly created items resolve correctly:
- taskIdMap — maps temporary task-link IDs to permanent Polarion IDs
- itemIdMap — maps temporary single-item-link IDs to permanent IDs
- itemLinkIdMap — maps temporary multi-item-link IDs grouped by column ID
Work Item Update
Both methods preprocess linked-item references to resolve any temporary IDs to permanent Polarion IDs before persisting changes.
Work Item Deletion
Cross-Project Support
The data access layer handles work items from different Polarion projects using a qualifiedproject/itemId form. Project-less IDs are automatically qualified with the active project identifier when an operation crosses project boundaries.
Transaction Management
All create, update, and delete operations are wrapped in transactions withbegin, commit, and rollback handling. If any part of a bulk operation fails, the entire transaction is rolled back so that partial updates are never persisted.
Risksheet does not maintain its own data store. All data lives in Polarion work items, subject to Polarion’s authorization and audit infrastructure. Risksheet visualizes and edits Polarion data — it does not store data separately.
Multi-Item Link Payload
multiItemLink columns accept arrays of linked item references in the request body. Each entry can carry a temporary ID (prefixed with *) that is resolved during the transaction, alongside references to existing Polarion items.
Related Pages
- Column Type Reference — column type definitions and behaviors
- Data Types — detailed data type specifications
- Suggestion and Autocomplete API — autocomplete and search endpoints
- Query Syntax — query filter syntax reference