You’re offline. This is a read only version of the page.
3
So, I know how to make a simple approval flow, and I can even make one with multiple approvers - but I'm having issue developing one for this specific reason.
I work in healthcare. Often we have folks need to submit documentation for a review from an expert that can say yay or nay on if it qualifies or not. Problem is, we don't make money just rejecting stuff and then saying no to the doc or patient. So typically folks will go and get what was needed, and then they submit another document, and then we look at that, and then we often approve if they get what we need.
So, needing a flow where someone submits a form, it puts that data in a list, we give an approval (approve vs reject), and THEN the user has the ability to go back and add additional documents to the same request WITHOUT having to re-enter the form.
The only way I can think of to do this is to do the list in a team where the whole company has access to edit anything, and that's a problem - as my company is huge. Like 10,000+ employees - so it could get messy with everyone having access to edit the form or add attachments on any form submitted.
Wondering if anyone here has designed anything remotely similar or if there's some other way of thinking or going about this that I'm not aware of?
This is my first post here so hello everyone. 😁
You could have a second form that only deals with resubmissions. And in the resubmission form they have to put their previous requestID (aka List ID) as well as their name or whatever.
Then when the form is submitted it searches the list for the same ListID that was included in the form, it also double checks matches by user name or email or whatever, just in case they put the incorrect ID number and then it will put the documents into the same request.
You could manage getting the listId number to the end user by sending it in the rejection email or notice.
Just brain storming
Share
Report
All responses (
Answers (
