Skip to main content

​
Before You Begin

You need:
  • Polarion Administrator role (not just Project Admin)
  • Access to Administration → Projects in Polarion
  • VPN connection to Polarion server (if working remotely)
  • Backup of project before modifying properties (see Backup and Restore Project)

​
Configure Project Properties

​
1. Access Project Properties

  1. Navigate to Administration → Projects in Polarion top menu
  2. Select your TestAuto2 project from the project list
  3. Click Edit Properties in the toolbar
  4. The Properties editor opens showing all project-level configuration keys

​
2. Set Core Project Identity

Configure basic project metadata:
Property KeyValuePurpose
project.nameTestAuto2 - Automotive Safety SolutionDisplay name in UI
project.idTestAuto2Unique identifier (cannot change after creation)
project.prefixTA2Work item ID prefix (e.g., TA2-123)
project.leadsafety-manager@company.comDefault project lead user ID
project.startDate2026-01-15Project start date (ISO format)
The project.prefix property determines work item ID format (e.g., TA2-123). Changing this after work items exist breaks all external references, Risksheet formulas, and PowerSheet queries. Only set during initial project creation.

​
3. Configure Document Type Defaults

Set default document types for each space: 
project.defaultDocumentType.Requirements=systemRequirementsSpecification
project.defaultDocumentType.Design=functionsSpecification
project.defaultDocumentType.Risks=riskSpecification
project.defaultDocumentType.Testing=testsSpecification
project.defaultDocumentType.Documentation=generic
This ensures new documents created in each space get the correct type automatically, which drives:
  • Risksheet configuration loading (riskSpecification documents auto-load .polarion/documents/risksheet.json)
  • PowerSheet RTM model filtering (documentType='systemRequirementsSpecification' in YAML queries)
  • Workflow assignment (each document type has its own workflow XML)

​
4. Set Nextedy Solution Properties

Configure TestAuto2-specific behavior:
Property KeyValuePurpose
nextedy.solution.nameTestAuto2 - Automotive Safety SolutionSolution branding in footer/dashboards
nextedy.solution.version2.0.0Solution version displayed in Home dashboard
nextedy.solution.vendorNextedy Systems s.r.o.Vendor name for licensing/support
nextedy.license.key[contact Nextedy for key]Commercial license activation key
nextedy.risksheet.defaultConfig.polarion/documents/risksheet.jsonDefault Risksheet config path
nextedy.powersheet.modelPath.polarion/nextedy/models/RTM domain model directory
Update nextedy.solution.version after each configuration deployment to track which projects are running which solution versions. Display version in Home dashboard via $project.getCustomField('nextedy.solution.version') Velocity expression.

​
5. Configure Workflow Transition Notifications

Enable email notifications for workflow state changes: 
project.workflow.notifications.enabled=true
project.workflow.notifications.recipients=project_approver,project_lead
project.workflow.notifications.events=approved,published,reworkRequested
This sends automatic emails when:
  • Risk specification documents transition to approved status (triggers notification to project_approver role)
  • Documents are published (alerts project_lead)
  • Rework is requested during review (notifies document author)

​
6. Set Custom Field Visibility

Control which custom fields appear in work item forms: 
project.customFields.visible.Hazard=severity,exposure,controllability,asil,safetyGoals
project.customFields.visible.FailureMode=sev,occ,det,ap,occNew,detNew,apNew
project.customFields.visible.Characteristic=nominalValue,lowerTolerance,upperTolerance,scccClassification
This overrides global custom field visibility to show only relevant fields per work item type, reducing form clutter.
Setting project.customFields.visible controls form layout visibility, but fields remain editable in Risksheet cells. To enforce read-only, use Risksheet column-level readOnly: true in .polarion/nextedy/sheet-configurations/*.yaml.

​
Verify Configuration

​
Check Property Application

  1. Navigate to Home dashboard
  2. Verify Solution Version displays correct value from nextedy.solution.version
  3. Create a new work item → verify ID prefix matches project.prefix (e.g., TA2-456)
  4. Create a new document in Risks space → verify document type defaults to riskSpecification

​
Validate Workflow Notifications

  1. Create a test Risk Specification document
  2. Transition to In Review status
  3. Verify project approvers receive email notification
  4. Check email contains document link and workflow state

​
Test RTM Model Path

  1. Open any PowerSheet (e.g., Whole RTM Sheet)
  2. Verify PowerSheet loads without modelPath not found errors
  3. Check browser console for warnings (F12 → Console tab)

​
Common Configuration Patterns

​
Multi-Project Environment

When running multiple TestAuto2 instances (e.g., per product line): 
project.id=TestAuto2-BrakingSystem
project.prefix=TA2B
nextedy.solution.instance=Braking-System-AEB
Use unique prefixes to prevent ID collisions when cross-project linking.

​
ISO 26262 Compliance Mode

Enable strict traceability and approval enforcement: 
project.compliance.mode=ISO26262
project.traceability.enforceUpstream=true
project.workflow.allowPublishWithoutApproval=false
project.signatures.required=project_approver,safety_manager

​
Development vs Production

Use different property sets per environment:
PropertyDevelopmentProduction
project.workflow.notifications.enabledfalsetrue
nextedy.solution.version2.0.0-dev2.0.0
project.compliance.modenoneISO26262

​
Troubleshooting

Problem: PowerSheet fails to load with “RTM model not found” error
Solution: Verify nextedy.powersheet.modelPath points to directory containing *.yaml model files. Check path is relative to .polarion/ root. Problem: Workflow notifications not sending
Solution: Check SMTP server configuration in global Polarion settings (Administration → Mail Settings). Verify project.workflow.notifications.recipients contains valid role IDs or user IDs. Problem: Work item IDs still show old prefix after changing project.prefix
Solution: project.prefix only affects new work items. Existing IDs cannot be changed. If you need to change prefix, create a new project and migrate work items.

​
See Also