Skip to main content

​
How Powersheet Embeds in Polarion

Powersheet registers itself as a web application within Polarion’s embedded application server. When Polarion starts, Powersheet’s plugin descriptor registers the application under the /polarion/nx_databridge/ URL path, making all Powersheet endpoints available through Polarion’s standard authentication and security infrastructure. diagram All requests to Powersheet are secured through Polarion’s authentication realm. Users must be authenticated Polarion users to access any Powersheet endpoint.

​
Key Integration Points

​
Administration Pages

Powersheet extends Polarion’s administration interface with dedicated management pages, accessible at multiple scope levels (global, project group, and project):
Admin PagePathPurpose
Domain ModelsAdministration > Nextedy POWERSHEET > Domain ModelsCreate and edit domain model YAML files
Sheet ConfigurationsAdministration > Nextedy POWERSHEET > Sheet ConfigurationsManage sheet configuration YAML files
SetupAdministration > Nextedy POWERSHEET > SetupInitial Powersheet configuration
LicenseAdministration > Nextedy POWERSHEET > LicenseLicense management
Each administration page supports three scope levels: repositoryScope (global), projectGroupScope, and projectScope. This allows configurations to be managed at the level that makes sense for your organization.

​
Document Integration

Every powersheet is anchored to a Polarion LiveDoc document. The document’s nextedySheetConfig custom field references the sheet configuration file to use. This field is populated through a dynamic enum provider that scans for available configuration files in both global and project-specific locations. The document URL parameter identifies the Polarion document path in folder/name format, and the project parameter specifies the Polarion project ID. Powersheet registers a navigation extension that adds Powersheet Drive as a topic in the Polarion sidebar. By default, it lists all documents of type powersheet. This can be customized through the project property: 
com.powersheet.powersheetDocumentQuery=type:powersheet OR HAS_VALUE:templateDoc.KEY

​
Entity Type to Work Item Mapping

The domain model bridges Powersheet’s entity types to Polarion’s work item types through the polarionType property: 
domainModelTypes:
  SystemRequirement:
    polarionType: systemRequirement
When a query is executed, the server API translates it into a Polarion Lucene query scoped to the specified work item type. Entity properties map to Polarion custom fields and built-in fields, and relationships map to Polarion link roles.
All configuration files — domain models and sheet configurations — are stored in Polarion’s SVN repository. Changes are version-controlled and visible in Polarion’s revision history.

​
Revision and Baseline Support

Powersheet supports viewing data at historical revisions and baselines. The revision URL parameter specifies which revision to display. Historical revisions are read-only — users can view past states of the data without risk of modification.

​
Security and Permissions

Powersheet inherits Polarion’s security model. Entity-level permissions control which entity types a user can query, and property-level permissions (the readable and updatable flags in the domain model) control field visibility and editability within the sheet.
The exact permission enforcement behavior at the property level may vary by configuration. Test your domain model’s readable and updatable settings to confirm expected behavior.

​
Server Endpoints

Powersheet exposes several HTTP endpoints within the Polarion web server:
EndpointPurpose
/polarion/nx_databridge/powersheetConfigRetrieves sheet configuration YAML
/polarion/nx_databridge/sheetsMain data operations (queries, updates)
/polarion/nx_databridge/permissionsUser permission information
/polarion/nx_databridge/documentDocument metadata retrieval
/polarion/nx_databridge/admin/*Administration interface
/polarion/nx_databridge/drive/api/*Powersheet Drive API
Source Code
  • prod-powersheet-src/com.nextedy.powersheet.client/src/modules/DocumentProvider/DocumentProvider.tsx
  • DomainModelTypeV2.java
  • plugin.xml
  • SchemaGenerator.java
  • web.xml