Share
ReportHi All,
My organization has decided to create a central repository to host company policy and process documents. We have agreed to capitalize Microsoft office software suite to achieve this goal. I have mentioned the user story explaining the current solution and the challenge I see in it.
User story:
User journey will start by uploading the document on source document library on SharePoint. Here after the scheduled flow will run executing certain checks on status (meta data column) field to filter newly uploaded documents. Then approval action will get triggered next [Start and wait for approval] and as expected document approver [SME] will get notification on outlook and teams for approval. The flow will now wait for approvers response to proceed further to subsequent actions.
Challenge:
We don’t want the flow to be in running state until the approver responds. But on contrary can we design a flow which resumes from actions next to Start and Wait for Approval Action whenever the approver responds.
I have already tried exploring ‘Configure Run After’ and ‘Time out’ settings associated with the action. I would also appreciate any comments on resource constraint in case of too many [100-200] flows in running state.
All responses (
Answers (
1,005
