New article
Recently updated
Troubleshooting inability to remove a field from the Required to Route section in a workflow step
Who is this article for?
Administrators responsible for managing workflows
Administration permissions are required.
Sometimes, removing a field from the Required to Route section in a workflow step doesn't save. The field reappears when the workflow is reactivated.
This article outlines the issue, affected versions, and how to fix it.
1. Issue
In version 2025.3.0.0, removing a field from the Required to Route list may not persist after publishing the workflow. This known defect affects workflows created by copying or cloning existing definitions.
The WF_ResponsibleParties table may still reference the original StateFieldId, causing the backend to restore the removed field despite UI changes.
The issue was fixed in version 2025.3.1.0, but workarounds exist for earlier versions.
2. Workaround
2.1. Re-add the affected field
To resolve the issue temporarily:
- Open the workflow definition.
- Identify the personnel custom field causing the issue.
- Completely remove the field from the workflow.
- Click Save.
- Re‑add the same custom field to the workflow.
- Adjust view/edit permissions as needed.
- Click Save.
- Set the workflow as Online.
This refreshes database references and resolves the stale routing linkage.
2.2. Remove the affected field from each route
This approach may work for some configurations but does not resolve the issue in all instances.
To resolve the issue temporarily:
- Open the workflow definition.
- Navigate to each route affecting the workflow step.
- Open route details.
- Untick the field under Required for Route.
- Click Save.
- Repeat for all other routes referencing the field.
- Click Save.
- Set the workflow as Online.
If the issue persists, try the previous workaround.