Hello @merwan
Let me take advantage of the fact that you are a senior program manager for Flow... 🙂
This is what my ideal scenario would look like:
1. A user creates a new list item and gives it the status 'Pending' in a choice field 'Status'. Data is still missing, so we cannot start an approval flow for management yet.
2. The user has collected the necessary data and sets the choice field 'Status' to 'Pending Approval'. A customized flow (so not one of your templates, but a flow started from a template, but modified or created from blank) is kicked off. If approved the choice field 'Status' is automatically changed to 'Visit Approved'.
3. Once the visit is approved a budget needs to be allocated and approved. The choice field 'Status' is changed to 'Pending Budget Approval' and a second approval flow is kicked off. If approved the choice field is changed to another value again.
This is of course the ideal scenario.
I would already be very happy with a situation whereby a user can select an item in a list, kick off a specific flow we built and have a column of the type 'Yes/No' swiched from yes to no (I know that this works since I build a flow that does that). In my scenario I would then have a 'YES/NO' column called Visit Approved and a second one called 'Budget Approved'. The real status column would need to be modified manually by the user.
Thank your for your thoughts on this.
Regards
Wim