As an approver, I want my submitter to redo the form fields if I reject it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2024 02:04 PM
Hello everyone,
As an approver, I want my submitter to be able to update the form he submitted with notes I provide.
The notes aren't necessary, but would be nice.
I thought I would use the "Rollback to" workflow, however, I am not sure how or if this would work.
Expanded use case:
Only Fulfillers can submit this form, if the manager rejects it, I want the fulfiller (who is really the submitter) to be able to edit it and resubmit the form again for approval.
Thank you in advance.
Nick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2024 03:35 PM
Hi @Nicholas Hromya,
You can add next approval after the rejection and trigger an notification for submitter to update the RITM,
adding rollback option and creating a catalog task ( just ) for editing the original RITM not a good approach as it will incident the steps and workflow , i am sure , after the update RITM , approver need to review the update and approve it for task otherwise, first time rejection is not adding any value.
You can create a new state for RITM and in case of rejection set the stage as "ReDo" and when user update the RITM with state "Re-Approve Request" , workflow will trigger the next approval. This process will continue until RITM not approve.
-Thanks,
AshishKM
Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2024 03:54 PM
Hello @AshishKM
When "adding rollback option and creating a catalog task" how would I assign this task to the submitter? I am not sure where in the task I can assign it to the submitter...
Thanks
Nick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2024 04:04 PM - edited 03-07-2024 04:07 PM
I don't get it , why submitter need a task. Submitter has already request and need the approval.
If something not correct, then keep the same RITM open for update and let the submitter update ( as per approver comment ) the same RITM and submit for re-approval.
so how submitter know about "Re-Work" , trigger the email for submitter once its rejected and change the RITM state as "ReWork".
After submitter update the RITM and change the state as "Re-Approval", you can check this "Re-Approval" state in workflow and link the approval block again. .... rest the approved path you already have in workflow.
so play on state value not the rollback.
Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2024 04:23 PM
Hello @AshishKM
Thank you for the reply.
The approving manager wants their submitters/fulfillers who are SMEs on a technical subject (like a service is down) to send out a notification to the department. But the managers don't want to write the notification, they only want to approve it to send it out.
If the approving manager doesn't like it, the approving manager wants the SME to re-write it.
I hope that helps.
Thanks
Nick