Skip to main content

Common Causes

Document creation failures typically occur due to:
  • Missing folder or invalid folder path
  • Insufficient user permissions
  • Template access restrictions
  • Duplicate document names
  • Configuration errors in templates

Verify Folder Exists

Nextedy RISKSHEET requires a valid folder path to create documents:
  1. Navigate to your Polarion project
  2. Go to Documents > Browse Documents
  3. Verify the target folder exists in the document tree
  4. Note the exact folder path (case-sensitive)
The document creation endpoint validates that the folder parameter is non-empty. Attempting to create a document without specifying a folder will fail immediately with a validation error.

Check User Permissions

You need specific Polarion permissions to create documents:
  1. Verify you have Create Document permission in the target project
  2. Check that your role allows document creation in the target folder
  3. Confirm you are not restricted to read-only access
RoleDocument Creation Rights
Project AdminFull document creation rights
Author RoleCan create in assigned folders
ContributorMay be restricted to specific folders

Verify Template Access

Template visibility depends on project-level permissions:
  1. Open Polarion Administration
  2. Navigate to the project where Risksheet templates are stored
  3. Check Permissions > User Roles
  4. Verify your user or role has access to the template project
Users cannot see or use Risksheet templates from projects they don’t have access to. If templates appear missing from the creation wizard, verify you have at least read access to the project containing the templates.

Check for Duplicate Names

Polarion prevents creating documents with duplicate names in the same folder:
  1. Browse to the target folder in Polarion
  2. Search for existing documents with your intended name
  3. Choose a unique document name or delete the conflicting document
  4. Retry document creation with the unique name

Validate Template Configuration

Corrupted or misconfigured templates can prevent document creation:
  1. Navigate to Administration > Risksheet Templates
  2. Open the template you’re trying to use
  3. Check that the template’s risksheet.json has valid JSON syntax
  4. Verify required properties exist: columns, dataTypes, levels
If you’ve configured custom template paths using nextedy.risksheet.templates.path, ensure the path points to a valid Polarion location and that templates are properly installed at that location.

Review Server Logs

For persistent creation failures, check Polarion server logs:
  1. Access your Polarion server file system
  2. Navigate to {POLARION_HOME}/data/logs/
  3. Open the most recent polarion.log file
  4. Search for errors containing “RisksheetViewServlet” or “document/create”
  5. Look for specific error messages about permissions, validation, or transaction failures

Target Document Creation Feature

If you’re trying to create work items that should be saved to specific documents, verify your configuration includes the createInDocument property:
{
  "id": "upstreamReq",
  "type": "itemLink",
  "header": "Requirement",
  "binding": "linkedRequirement",
  "canCreate": true,
  "createInDocument": "Requirements Specification",
  "typeProperties": {
    "type": "requirement",
    "project": "ProjectA"
  }
}
The createInDocument property (added in version 24.8.1) specifies where new linked items should be created, independent of which documents are loaded in the query.
The query, document, and project properties control which items are loaded and displayed. The createInDocument property controls where new items are saved. These are independent settings, allowing you to load items from multiple documents while always creating new items in a specific target document.

Workflow Action Errors

If document creation succeeds but workflow initialization fails:
  1. Check that the template’s initial workflow status is valid
  2. Verify workflow actions are defined for the document type
  3. Ensure required fields for the initial status are present in the template

Verification

After resolving the issue, you should see:
  • Document creation wizard completes without errors
  • New document appears in the target folder
  • Document opens successfully in Nextedy RISKSHEET
  • Template configuration is applied correctly
  • You can create and save work items in the new document

See Also

KB ArticlesSupport TicketsSource Code
  • RisksheetViewServlet.java
  • WorkflowActionServlet.java
  • ExportToPdf.ts
  • NewBaselineCommand.ts
  • StatusChangeCommand.ts