Skip to main content
This page covers document creation issues identified from source code analysis. Some scenarios may vary depending on your specific Polarion and Risksheet version.

Symptoms

  • The “Document NOT created” pop-up message appears after attempting to create a new document
  • The creation wizard fails silently without producing a document
  • Error message “You do not have permissions to create new items.” appears
  • Workflow status change fails with “There are unsaved changes. Please save the document first.”

Check Folder Selection

The document creation wizard requires a non-empty folder selection. If you receive an error:
  1. Open the Risksheet home page (document selection interface)
  2. Select a valid folder from the available folder list
  3. Enter a document name
  4. Select a template
  5. Click Create
diagram
The creation wizard validates that a folder is selected. If no folder is specified, document creation fails. Ensure you select a target folder before clicking Create.

Check Permissions

If you see the error “You do not have permissions to create new items.”:
  1. Verify your Polarion user account has create permissions for work items in the target project
  2. Check that you have write access to the folder where the document will be created
  3. Confirm your Risksheet license is active and not in reviewer/read-only mode
Permission LevelCan Create DocumentsCan Edit
Full license + project write accessYesYes
Reviewer licenseNoNo (read-only)
No license + project accessNoNo (read-only)
The admin permission check can be bypassed by setting nextedy.risksheet.disable_admin_check=true in the Polarion configuration properties, but this should only be used for troubleshooting purposes.

Check Template Configuration

The template selection affects the initial document structure. If a document is created but appears empty or misconfigured:
  1. Verify the selected template exists and contains a valid risksheet.json attachment
  2. Check that the template path is configured in the project Risksheet settings
  3. Confirm you have read access to the project containing the template
Template paths are configured via project properties. The default template path is Risks/Risk Specification. Multiple paths can be comma-separated to allow document creation in several locations.
When using templates from a different project, ensure all users have read access to the template project. Missing permissions can cause documents to be created with an incomplete or broken configuration rather than showing an explicit error.

Fix: Template Installation Issues

If no templates are available in the creation wizard:
  1. Navigate to the Risksheet administration page
  2. Run the template installation via the Setup function (POST /admin/setup endpoint)
  3. Verify the templates appear in the template list after installation
The setup function installs default Risksheet templates and returns a success or failure message.

Fix: Workflow Status Change After Creation

If you encounter “There are unsaved changes. Please save the document first.” when trying to change document status after creation:
  1. Save all pending changes in the Risksheet grid
  2. Verify no cells show dirty state indicators
  3. Retry the workflow status change
Document status changes are blocked when the grid contains unsaved edits. The system validates the clean state before sending the workflow action request. After a successful status change, the page automatically reloads to reflect the new document status and available actions.
If a document becomes inaccessible (deleted, moved, or permissions revoked), attempting workflow status changes returns the error “Document not accessible” with the document location. Verify the document still exists and you have access before retrying.

Verification

After resolving the issue:
  1. Navigate to the Risksheet home page
  2. Select a folder, enter a document name, and choose a template
  3. Click Create and confirm the document is created successfully
  4. Open the new document and verify the Risksheet grid loads with the template configuration
You should now see the new Risksheet document open with the selected template’s column layout, formulas, and styling applied.

See Also

KB ArticlesSource Code
  • RisksheetViewServlet.java
  • WorkflowActionServlet.java
  • ExportToPdf.ts
  • NewBaselineCommand.ts
  • StatusChangeCommand.ts