Summary

In the Purchase Order (PO) approval workflow, when an approver selects the “Request Change” option, the workflow fails to assign the resulting task to the delegated user. Instead, the task is incorrectly assigned to the original submitter, which in this case is the system account. This behavior prevents the delegated user from taking action and interrupts proper workflow progression.

Current Behavior

• When the approver selects “Request Change”, the system assigns the follow-up task back to the original submitter, which is the system account.
• A delegation has already been configured for the system account, but the workflow does not honor the delegation settings.
• After selecting “Request Change”, the workflow status immediately updates to “Rejected” instead of remaining In Progress or waiting for the change request action to be completed.

Expected Behavior

• The resulting task should be routed to the delegated user configured for the original submitter (system account).
• The workflow should remain active and reflect a status that indicates a pending change request from the submitter (or delegated user).
• The workflow should not automatically transition to “Rejected” unless explicitly rejected by the approver.

Impact

• Delegated users cannot access or respond to change request tasks.
• Workflow stalls, requiring manual intervention.
• Approval processes become inconsistent and operationally inefficient.
• Creates risk of unintended workflow rejections and delays in PO processing.