Find Configuration Files

​

Understanding Configuration Storage

​

Locating Document-Level Configuration

​

Check Document Attachments

1. Open your Risksheet document (LiveDoc) in Polarion
2. Navigate to the Attachments section at the bottom of the page
3. Look for a file named risksheet.json
4. If present, this configuration takes precedence over template and built-in configurations

​

View Configuration Source

1. Open your Risksheet
2. Go to Menu > Configuration > Edit Risksheet Configuration…
3. The editor toolbar shows the configuration source:
   • From Template: Displays template document name if inherited
   • Document-Specific: Indicates configuration is attached directly to the document
   • Built-In: Shows when using default configuration

​

Locating Template-Level Configuration

​

Find the Template Document

1. Open your Risksheet document in Polarion
2. View the document’s Custom Fields section
3. Find the templateDoc custom field
4. The value shows the path to the template document (e.g., Risks/Risk Specification)
5. Navigate to that document in Polarion’s document browser

​

Check Template Attachments

1. Open the template document identified above
2. Navigate to the Attachments section
3. Look for risksheet.json
4. This configuration is shared by all Risksheets using this template

​

Configuration File Paths Reference

​

Identifying Active Configuration

​

Using the Configuration Editor

1. Open Menu > Configuration > Edit Risksheet Configuration…
2. Check the tab title:
   • Shows template name if configuration is inherited
   • Shows document name if configuration is document-specific
3. Review the config history panel to see when configuration was last modified
4. The YAML mode displays the complete active configuration regardless of source

​

Checking Server Logs

1. Open the Risksheet
2. Go to Menu > Configuration > Edit Risksheet Configuration…
3. Check Polarion server logs (polarion/log/log.txt)
4. Search for entries containing:
   • DocumentConfigProvider
   • risksheet.json
   • Configuration file path resolution messages

​

Common Configuration Issues

​

Configuration Not Loading

1. Verify the file is named exactly risksheet.json (case-sensitive)
2. Check that the file is attached to the correct document or template
3. Clear browser cache and reload the Risksheet
4. Verify the templateDoc custom field points to the correct template

​

Multiple Versions Causing Conflicts

1. Check if both document and template have risksheet.json attachments
2. Remember document-level configuration overrides template configuration completely (no merging)
3. Use Override Template only when full customization is needed

​

Template Changes Not Reflected

1. Verify the Risksheet document doesn’t have its own risksheet.json attachment
2. If document-level configuration exists, remove it or use Revert to Template option
3. Refresh the Risksheet after template changes

​

Verification

• Locate the active risksheet.json file for any Risksheet
• Determine whether configuration is document-level or template-level
• Identify the template document path from custom fields
• Use the Configuration Editor to view configuration source

​

See Also

• Use the Configuration Editor - Edit configuration through the UI
• Override Template Configuration - Switch between template and document-specific configuration
• Set Up Global Templates - Create reusable configuration templates
• Configuration System - Understand configuration architecture
• Configuration Hierarchy - Learn how configuration inheritance works
• Risksheet.json Format - Configuration file structure reference