In an invoice approval workflow with conditional decisions, it should be possible that when rejecting the approval or requesting a change, the entire workflow checks the conditional decisions again after the change and is then reassigned to the person who should receive the workflow according to the criteria of the conditional decision. 

Currently the behavior of the Invoice Approval Workflow used from pending invoices goes directly to the last approver (who made the request change) - but not again from the beginning through the conditional decisions of the workflow. 

Example:

The first step checks whether the invoice is above or below a certain amount.

If the amount is above this threshold, the invoice will be sent to a specific approval group (e.g. A, B).

This Group should be able to approve and reject or request change to send the workflow to the creator for a change.

Group A (Cost center A) receives the invoice after the workflow checks and sends it back to the creator with a change request, because the invoice should be for another cost center e.g. for Cost Center B.

The creator of the Invoice changes the dimension of the cost center so that Group B should receive the invoice after the change to approve it.

However, as written earlier, the workflow will go back to Group A for approval because the current workflow behavior does not recheck the workflow's conditional decision to assign the modified invoice to the correct approver. 

To ensure that within such a process the change ends up with the correct group or person it is extremely important to fix this bug.

This scenario occurs in practice in many companies and should be implemented in the workflow engine as soon as possible.