For an approval task, the approver can request a change to one or more field values.

When a change is requested, the workflow task where the field value was originally entered is reactivated with the original assignment.

The reactivation and reprocessing logic depend on the Skip change request steps with no changes field in the General section of the Data entry workflow template details page.

In this field, you can select one of these options:

• No: The reactivated workflow task and all subsequent workflow tasks must be redone.
• Yes: The reactivated workflow task and only the subsequent workflow tasks for which field changes are requested must be redone.

Behavior when ‘Skip change request steps with no changes’ is set to Yes

The workflow tasks that must be redone are identified automatically.

Only tasks with fields for which changes are requested must be redone.

Workflow tasks without fields for which changes are requested are skipped.

The behavior of a reactivated workflow depends on how the workflow template steps are organized (see table):

Step organization	Behavior
Sequential	Impacted tasks are reactivated in the order defined in the workflow template. Each task must be completed before the next begins. The approval tasks starts only after all relevant tasks are completed.
Parallel	If impacted tasks belong to parallel branches, they are reactivated at the same time. The approval task starts only after all impacted parallel tasks are completed.
Conditional	If a changed field affects a conditional path, the conditions are re-evaluated after the related task is completed. Based on the updated condition, the correct branch is triggered automatically. Tasks not relevant to the new condition are skipped.