Request Revisions & Versioning

Request Revisions & Version History lets you fix a request an approver sent back instead of filing a new one from scratch. Editing and resubmitting creates a new version linked to the original, so the whole chain stays together and prior field values and uploaded files carry forward unless you change them. This guide is for the Requester working a returned request; you'll need a denied or revision-requested request of your own on screen. Resubmission is turned on per flow, and only the latest version in a chain can be resubmitted.

Who this is for: user.

Edit and resubmit the request as a new version

When an approver denies a request or asks for a revision, this is how you correct the specific problem they raised and send it back without re-entering everything — prior field values and uploaded files carry over. Cancelled requests have no resubmit entry in the UI, and an optional cap on chain length can limit how many times a request can be resubmitted.

Sign in as the Requester who submitted the request.
On the request page, click Edit & Resubmit to reopen the request's fields for editing.

Step 2
Update the field the approver flagged — for example, revise the text in Item to describe what changed (the example uses Standing desk (vendor quote attached)).

Step 3
Click Review & Resubmit to move to the confirmation step.

Step 4
In Reason for resubmission (optional), note what you changed so the approver can see it at a glance — e.g., Vendor quote attached as requested.

Step 5
Click Confirm Resubmission to submit the new version.

Step 6
Click Close to dismiss the confirmation.

Step 7
Click My Requests to return to your list of requests.

Step 8
Open the resubmitted request from the list — in the example screenshots it appears as Standing desk (vendor quote attached).

Step 9

On the request page you'll see the version marker v2 (current), confirming the resubmission created a new version in the same chain.