Skip to main content

​
Step 1: Open the Domain Model

  1. Navigate to Administration > Nextedy POWERSHEET > Domain Models
  2. Select the domain model to edit
  3. Locate the domainModelTypes section

​
Step 2: Map a Single Work Item Type

Add the polarionType property to an entity type to map it to a Polarion work item type: 
domainModelTypes:
  UserNeed:
    polarionType: userNeed
    properties:
      description: ~
      severity: ~
The polarionType value must match the exact Polarion work item type ID (typically lowercase first letter by convention).
If you do not specify polarionType, Powersheet uses the entity type name with a lowercase first letter as the Polarion type. For example, UserNeed maps to userNeed automatically. Only specify polarionType when the names differ.

​
Step 3: Map Multiple Polarion Types to One Entity

The polarionType property accepts either a single string or an array of strings, allowing one domain model entity to represent multiple Polarion work item types: 
domainModelTypes:
  Requirement:
    polarionType:
      - systemRequirement
      - softwareRequirement
      - hardwareRequirement
    properties:
      description: ~
      severity: ~
This is useful when multiple Polarion types share the same structure and you want to display them in a single column hierarchy.

​
Mapping Reference

The following table shows mappings from the RTM example model. Your own model will use entity types and Polarion type IDs specific to your domain.
Domain Model EntitypolarionTypePolarion Work Item Type
UserNeeduserNeedUser Need
SystemRequirementsystemRequirementSystem Requirement
DesignRequirementdesignRequirementDesign Requirement
HazardhazardHazard
RiskControlriskControlRisk Control
diagram When defining relationships, the linkRole property maps to a Polarion link role. Ensure the link role exists in your Polarion project configuration: 
relationships:
  - from: UserNeed
    to: SystemRequirement
    cardinality: one-to-many
    storage: linkedWorkItems
    linkRole: refines
    direct:
      name: systemRequirements
    back:
      name: userNeeds
The storage: linkedWorkItems value tells Powersheet to use Polarion’s native work item link mechanism for persisting the relationship.
Go to Administration > Work Item Link Roles in Polarion and confirm that the linkRole value in your domain model matches an existing link role ID. Mismatched link roles cause relationship errors at runtime.

​
Step 5: Use the Complete RTM Example

Here is a standard RTM mapping with all five entity types: 
domainModelTypes:
  UserNeed:
    polarionType: userNeed
    properties:
      description: ~
  SystemRequirement:
    polarionType: systemRequirement
    properties:
      description: ~
      severity: ~
  DesignRequirement:
    polarionType: designRequirement
    properties:
      description: ~
  Hazard:
    polarionType: hazard
    properties:
      description: ~
      severity: ~
  RiskControl:
    polarionType: riskControl
    properties:
      description: ~
The exact Polarion work item type IDs depend on your project configuration. Check Administration > Work Item Types for the correct IDs.

​
Verify

After saving the domain model, open a powersheet document that uses this model. You should now see:
  • Entity types correctly load work items from Polarion matching the mapped types
  • Creating new items produces the correct Polarion work item type
  • Relationship pickers display items of the correct types

​
See Also

model.yaml, DomainModelTypeV2.java, SchemaGenerator.java, todosBig_model.yaml
Source Code
  • model.yaml
  • todosBig_model.yaml
  • DomainModelTypeV2.java
  • SchemaGenerator.java
  • todos_model.yaml