Power Platform Community Forum Thread Details

Hi everyone,

I am tasked with creating some sort of layered reporting algorithm, that is supposed to get automated as far as possible.
An incident happens somewhere in the firm, and the responsible Person is supposed to create some specifying element via PowerApps; so far, so good.
Now the next higher up person is supposed to be informed via workflow, given a choice whether to confirm or edit the incident. If confirmed/edited, it immediately gets send further up, otherwise it should be sent further up regardless after a certain time window.

What I want to know is whether this kind of thing is possible in Power Automate, to basically Combine (timer OR changeOfElement) like that and maybe a hint to which connectors/datatypes or events I should use for this, the specifics i'll somehow find out myself.

Thanks in Advance!
Best regards

(I apologize for random german spelling, my pc autocorrects everything I write to german and I didn't find out yet how to shut that off)

Categories:

General topics

Hello @Anonymous

I would say that it is possible to use Power Automate for this. See my draft flow diagram and data model.

Flow.Incident review actions and data model.png

The flow would trigger on any change to the Incidents - either by the responsible person registering an incident or this flow updating the incident.

You then identify if anyone has to review the incident - if none, then stop.

If a reviewer is found, request a review using Approvals - custom "Confirmed", "Edited" - where the reviewer enters any comment directly in the approval email. The Approval is setup with a timeout (Settings) as you need.

If the approval action times out, register the fact in the Incident reviews!

If the reviewer approve using the "Confirmed" option, register the fact in the Incident reviews.

If the reviewer reject using the "Edited" option, register the fact and the response comment in the Incident reviews.

Update the incident with the fact that a review took place by the reviewer (this will trigger another run by the flow and the next level review)!

Stop, as the flow has finished.

I am using a second list, Incident reviews, to hold the fact of a review taking place, so as allow for X number of reviews 🙂

Hope this helps you on the way.

Kind regards, John