Hello All Users,

When a Change Action is submitted for approval by selecting a route template, the workflow works for example as follows:
At Order 1, the Change Action is assigned to 10 approvers, and at Order 2, it is assigned to 2 approvers.
This means the Change Action should wait for all 10 approvers at Order 1 to either approve or reject before moving forward.

However, during this approval process, while the Change Action is still in In Approval state, the Change Action owner can easily move it back to In Work, even though the approval cycle is still ongoing.

From a process governance point of view, this does not seem correct.
If a data object is in an approval workflow, I would expect that it cannot be reverted to In Work until all approvals (or a rejection) at the current order level are completed.

Is there a standard configuration, setting, or best practice to prevent the Change Action owner from moving the object back to In Work while approvals are still pending?
Specifically, I want to ensure that approval comments and decisions at each order level are completed before the Change Action can be reverted.

Any guidance or experience on how to handle this would be appreciated.

Thanks in advance,
AKIN KUZEYİ