Skip to main content
See also: Domain Model Types | Properties | Relationships
This page has thin source coverage. Some behaviors described below should be verified in your Powersheet installation.

Mapping Overview

diagram

Core Mapping Properties

NameTypeDefaultDescription
polarionTypestring or arrayEntity type nameMaps the domain model entity type to one or more Polarion work item types. When omitted, the entity type name is used as the Polarion type.
polarionProtostringIWorkItemSpecifies the Polarion prototype (object type) this entity maps to. Determines which Polarion object types this entity can represent.

Single Type Mapping

The most common pattern maps one entity type to one Polarion work item type:
domainModelTypes:
  UserNeed:
    polarionType: userNeed
    properties:
      title:
      description:
When polarionType is omitted, the entity type name is used as the Polarion type ID. For example, an entity named Task with no explicit polarionType will map to Polarion work item type Task.

Multi-Type Mapping

A single entity type can map to multiple Polarion work item types by providing an array:
domainModelTypes:
  Requirement:
    polarionType:
      - sys_req
      - des_req
    properties:
      title:
      description:
      severity:
This configuration allows the Requirement entity type to represent work items of both sys_req and des_req types. Queries for this entity type will include both types.

Built-in Entity Types

Powersheet includes built-in entity types that map to Polarion objects other than work items:
Entity TypePolarion ObjectNotes
DocumentPolarion moduleContainer for work items. Not a work item itself.
ChapterPolarion headingDocument structure element for headings.
ProjectPolarion projectProject-level metadata.
These built-in types do not require polarionType and have specialized property handling.

Mapping Validation Rules

  • Entity type names must be single words without spaces or special characters
  • polarionType values must match work item type IDs defined in Polarion configuration
  • Relationship from/to fields must reference domainModelTypes names — not Polarion work item type IDs

RTM Mapping Example

Example RTM entity types with their Polarion mappings:
Entity TypepolarionTypePolarion Work Item Type
UserNeeduserNeedUser Need
SystemRequirementsystemRequirementSystem Requirement
DesignRequirementdesignOutputDesign Output
HazardhazardHazard
RiskControlriskControlRisk Control

Domain Model Schema Support

Powersheet provides a JSON schema for validating domain model configuration files. The schema includes:
  • Enumeration of valid Polarion prototype names for the polarionProto property
  • Support for both scalar and array formats for polarionType
  • Validation of required fields via schema constraints
Schema validation is available for IDE support and autocomplete when editing domain model YAML files. Check your Powersheet version for schema file location.

Complete YAML Example

domainModelTypes:
  Document:
    properties:
      title:
      type:

  Chapter:

  UserNeed:
    polarionType: userNeed
    properties:
      title:
      description:
      severity:
      component:

  SystemRequirement:
    polarionType: systemRequirement
    properties:
      title:
      description:
      severity:

  DesignRequirement:
    polarionType: designOutput
    properties:
      title:
      description:

  Hazard:
    polarionType: hazard
    properties:
      title:
      description:
      severity:

  RiskControl:
    polarionType: riskControl
    properties:
      title:
      description:

relationships:
  - from: UserNeed
    to: SystemRequirement
    cardinality: one-to-many
    storage: linkedWorkItems
    linkRole: refines
    direct:
      name: systemRequirements
    back:
      name: userNeeds

  - from: SystemRequirement
    to: DesignRequirement
    cardinality: one-to-many
    storage: linkedWorkItems
    linkRole: refines
    direct:
      name: designRequirements
    back:
      name: systemRequirements

Related pages: Domain Model Types | Properties | Link Roles | Model YAML Structure
Source Code
  • DomainModelTypeV2.java
  • todosBig_model.yaml
  • model.yaml
  • todos_model.yaml
  • sf_model.yaml