Hi @Anonymous ,
This is a tricky one, but we'll figure this out.
We could always include four approval steps right next to each other and between them store the results in SharePoint so that you can get the "First and Last name" and approval status.
But this can be an issue because if there is just 3 or 5, then we would have a problem. We need something independent of the number of approval steps.
Add in SharePoint 1 additional field that has the "Next Approver."
Then create a new Flow that sends the approval process and stores the result in SharePoint. Just that. You can call it using the "Request" trigger and just doing an HTTP Post to call it in the source Flow. You can pass the next approver parameter and the id of the field that you want to update in SharePoint.
The first Flow should trigger on changes and call the "Approval Flow." The second should update SharePoint with the next Approver.
If there is no "next approver," then the flow does nothing.
Since we're using a Flow to update the fields, you always have updated "Next Approver" so that your users know who to call. In the end, you'll have the result of the approval process.
Sounds a bit confusing but it's quite simple. To resume:
1. Add a field that stores the "Next Person."
2. Create a Flow "Whole Approval Process" that triggers when there are changes to that list
3. Create a Flow "Approval Flow" that receives a person and sends the approval process.
4. Call the "Approval Flow" within the "Whole Approval Process"
5. "Approval Flow" receives the result and stores in SharePoint.
6. Since there was a change, the "Whole Approval Process" triggers again.
Makes sense?
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Cheers
Manuel
