When a Change Request is raised on a Purchase Requisition, the workflow currently starts again from the very beginning, almost as if the requisition was canceled and resubmitted.

This happens when using Workflow > Change request, even for small or harmless changes such as updating quantities, dates, or financial dimensions.

While this might be the expected behavior today, it creates a lot of unnecessary friction in day‑to‑day procurement work.

What’s the problem?

Restarting the workflow every time a change is made means:

• All previous approvers must approve again, even when nothing relevant changed
• Procurement processes are delayed
• Approvers get frustrated approving the same requisition multiple times
• Small changes turn into long approval cycles
• The overall user experience feels heavy and inefficient

In many cases, the change does not invalidate the earlier approvals, yet the system forces a full restart anyway.

What we would like to see

Instead of restarting the workflow from the beginning, the system should allow the workflow to continue from where it left off, or at least from the relevant approval step.

For example:

• Resume the workflow from the last completed approval
• Re-trigger only the approval steps affected by the change
• Or provide a workflow setting that lets customers choose how change requests behave (restart vs. resume)

This would give customers the flexibility to match the workflow behavior with how their business actually works.

Why this matters

Change requests are meant to handle adjustments, not reset the entire approval process.

For organizations with multi‑level approvals and high volumes of purchase requisitions, the current behavior slows things down and creates unnecessary work for both requesters and approvers.

Allowing the workflow to resume after a change would make the process faster, more practical, and much closer to real‑life business needs.