Who is this article for?

Administrators who manage and configure workflow.

Alter Workflow permissions are required to edit workflow definitions.

This article explains how to troubleshoot and resolve the issue with fields reappearing in the Required for Route fields after putting the workflow online.

Issue

When you activate a workflow, the system checks its definition, including if any personnel custom field used as a Responsible Party at a step is also required for the route leading to that step.

If this isn't the case and "Automatically fix small errors" is enabled, the system automatically makes the field required again, causing it to reappear each time you activate the workflow.

Solution

To resolve the issue, remove the field from the workflow entirely and then re-add it. This resets the field's configuration and ensures it is saved correctly across all routes.

Important

Clicking Remove deletes a custom field from all workflow steps, not just the current one.

To hide a field on a specific step, leave it in the workflow but uncheck View and Edit for that step instead of removing it.

To re-add the field:

1. From Workflow Administration, find the affected workflow and take it offline if online.
2. Go to the step with the problematic Required for Route field.

3. In New Fields for this Step, remove the field by clicking Remove.

4. Click Save Changes to update the step.
5. Re-add the field via Create New Field or from available fields.
6. Set the field's View and Edit permissions as needed.
7. Click Save Changes again.
8. Check each route that required the field to ensure it’s no longer listed.
9. Return to the workflow page and select Put Online.

Note

If there are any errors in how the definition is configured, Ideagen Quality Management presents a list of where they occur before the workflow can go online. All errors must be resolved before the workflow will accept the Put Online action.

Tip

Enable "Automatically fix small errors" in the Workflows tab for Ideagen Quality Management to fix minor issues automatically.

For example, if a personnel custom field is used as a responsible party but isn't required for the preceding route.