Open dpdavids opened 5 months ago
I think the simplest solution here is to make the "submitted" state a mutable state. i.e. the user can just unsubmit, and the state goes back to draft. Should be too much more that a bit of policy logic and UI changes.
@dpdavids in regards to "if the travel has been approved the change needs to follow the same workflow as the original process"
Do you mean that the user needs to start the entire process over again? If that turns out to happen more frequently, I imagine I could build a "clone" procedure, that would take an existing travel authorization and re-generate it as a draft to save time.
Relates to:
Context
Is your feature request related to a problem? Please describe.
Describe the solution you'd like The traveler needs the ability to reassign the travel authorization request back to themselves to make changes to dates, estimates, travel advances, travel locations, etc. The traveler should be able to select a button that says "revert to draft" if they need to update the request. Maintain the audit trail of the changes.