Risk Deletion Errors - Nextedy Documentation

Symptoms

Error / Behavior	Likely Cause
`No rejected action found` in console	Workflow transition missing for current item status
Manually created items delete, but imported items fail	Imported items have a different initial workflow state
`RISKSHEET rollbackTx` in server logs	Deletion operation failed and was rolled back
Items remain in grid after remove action	`rejectedAction` / `rejectedStatus` misconfigured
`resolution` field cannot be edited in grid	Field is always read-only in Risksheet

Understand Removal Strategies

Risksheet supports two removal approaches configured via the dataTypes.risk.removeStrategy property:

The default removeStrategy is delete, which permanently removes the work item. For regulated environments where audit trails are important, use the workflow-based approach:

{
  "dataTypes": {
    "risk": {
      "type": "fmea_risk",
      "removeStrategy": "delete",
      "rejectedAction": "reject",
      "rejectedStatus": "rejected",
      "rejectedResolution": "invalid"
    }
  }
}

Property	Default	Purpose
`removeStrategy`	`delete`	Strategy for removing risk items
`rejectedAction`	`reject`	Workflow action to execute on removal
`rejectedStatus`	`rejected`	Target status after rejection
`rejectedResolution`	`invalid`	Resolution value set on rejection

Fix 1: Resolve “No Rejected Action Found”

The error No rejected action found occurs when Risksheet attempts to execute a workflow action that does not exist for the work item’s current status.

Open the browser developer console (F12)
Attempt the delete/remove operation
Look for the No rejected action found error
Check the work item’s current status in Polarion
Verify that a workflow transition matching your rejectedAction value exists from the current status

Work items imported via the Polarion tracker importer (for example, from Excel) may have a different initial workflow state than items created through Risksheet. Ensure the workflow definition includes a rejection transition from all possible initial states, including the state assigned during import.

Fix 2: Configure Workflow for Deletion

To use workflow-based removal, your work item type’s workflow must include:

A transition (action) matching the rejectedAction value from every status where removal should be possible
A target status matching the rejectedStatus value
The rejectedResolution value must be a valid resolution option for the target status

Property	Config Value	Workflow Requirement
`rejectedAction`	`reject`	Action “reject” exists as a valid transition from all applicable statuses
`rejectedStatus`	`rejected`	Status “rejected” exists in the workflow
`rejectedResolution`	`invalid`	Resolution “invalid” is valid for the rejected status

The Polarion resolution field cannot be directly edited in Risksheet — it is always read-only. Use the rejectedAction, rejectedStatus, and rejectedResolution properties to handle rejection workflows automatically instead.

Fix 3: Handle Electronic Signature Requirements

Electronic signatures are not supported in Risksheet because the Polarion API does not expose this capability. If your process requires signatures when rejecting items:

Remove the signature requirement from the rejection action used by Risksheet
Create a separate Polarion workflow action with the electronic signature requirement
Perform the signature-required action outside Risksheet through the standard Polarion interface

The electronic signature limitation is due to missing Polarion API support. Check whether newer Polarion versions have added API support for electronic signatures.

Task Unlinking vs. Deletion

Risksheet distinguishes between deleting a risk item and unlinking a task relationship:

Standard deletion — removes the actual work item from Polarion permanently
Task unlinking — removes the relationship between the risk item and the linked task without deleting either work item

All deletion and unlinking operations are transactional. If an operation fails, the system automatically rolls back to prevent partial updates.

Verification

After applying the configuration changes, you should now see:

Risk items removed from the grid after clicking the remove action
If using workflow-based removal, items transition to the rejectedStatus and are filtered from the grid view
No No rejected action found errors in the browser console
Both manually created and imported items can be removed successfully

To confirm the status change, open the work item directly in Polarion and verify its status and resolution values match the configured rejectedStatus and rejectedResolution.

​Symptoms

​Understand Removal Strategies

​Fix 1: Resolve “No Rejected Action Found”

​Fix 2: Configure Workflow for Deletion

​Fix 3: Handle Electronic Signature Requirements

​Task Unlinking vs. Deletion

​Verification

​See Also

Symptoms

Understand Removal Strategies

Fix 1: Resolve “No Rejected Action Found”

Fix 2: Configure Workflow for Deletion

Fix 3: Handle Electronic Signature Requirements

Task Unlinking vs. Deletion

Verification

See Also