Unanswered

Start State or End state missing

(1) Share

Report

Posted on by DaHoWL

Hello Everybody!
First of all, thank you for your support in this forum.
For the question:

Input:

Key	Start State	End State	Start of First State	End of First State
REF-1903141	Analysis	Resolved	03/05/2024 09:28	04/05/2024 11:52
REF-1903149	Analysis	Rejected	03/05/2024 09:32	03/05/2024 10:42

Description

Flow with 2 cases with the same start & 2 different end states
We only have the duration of the Start State (“Analysis”)
The duration of the End State is infinite

Problem

We can only upload one State as “Activity” in Powerautomate
To calculate the mean duration of “Analysis”, we need to upload the Start State as Activity. This will not show "Resolved" or "Rejected" as end state.
To count the number of tickets reaching each End State, we need to upload the End State as Activity. This will lose the first status "Analysis"

How can we solve that?

Thanks a lot in advance!

Categories:

Recommendations

All responses (3)

Answers (0)

LukasCervenan 16 on at

Like (0)

Report

Start State or End state missing

Hello DaHoWL,

the obstacle here is with the EventLog creation. In order to do process mining, you need 3 basic attributes: CaseID, ActivityName and Timestamp.

In above case:

CaseID=Key

Timestamp = either Start or End, (but you can have both).

ActivityName = 2 columns? This will not work. You must have 1 column.

My proposal:

Rename "Start State" to simply "State". And fill it with values: Analysis or Resolved or Rejected. Just one of them.

Delete "End state", since this would be another "State", already addressed in "State" column.
Suggested answer

SudeepGhatakNZ 14,381 Most Valuable Professional on at

Like (0)

Report

Start State or End state missing

I agree with @Russ_PowerLS

You can use two separate flows or a combination of activities. The first flow logs the start state, "Analysis," as an activity when a ticket enters this state, storing the start time and ticket ID in a data store like SharePoint or Excel. The second flow logs the end state (either "Resolved" or "Rejected") when the ticket transitions, linking it to the "Analysis" activity using the ticket ID. This approach ensures both states are recorded and allows for further analysis using tools like Power BI or Excel.
Suggested answer

Russ_PowerLS 8 on at

Like (1)

Report
Start State or End state missing

Sounds like you don't have logging - but you may and not realize it where you track the date /time changes. But if you already went down that road
Create two separate Power Automate Flows

One flow that tracks the start state ("Analysis") and measures the time spent in that state.

A second flow that tracks the end state (either "Resolved" or "Rejected").

This means you'll have to run these flows independently and then combine the data manually or through a secondary system (like Power BI) where you can join the two sets of data by your key.

OR

Export both sets of data to Power BI or Excel, where you merge the two types of data (start state duration and end state counts) in a report. Power BI could then serve as the tool to merge these two aspects, calculating mean durations for "Analysis" and summarizing end states across tickets.

Community site session details

Start State or End state missing

Helpful resources

News and Announcements

Quick Links

Paul Stork – Community Spotlight

Congratulations to the June Top 10 Community Leaders!

Announcing the Engage with the Community forum!

Leaderboard > Power Automate

Featured topics

Product updates

Community site session details

Start State or End state missing

Helpful resources

News and Announcements

Quick Links

Paul Stork – Community Spotlight

Congratulations to the June Top 10 Community Leaders!

Announcing the Engage with the Community forum!

Subscribe to this forum!

Select categories

Leaderboard > Power Automate

Featured topics

Product updates