Skip to main content

Notifications

Power Platform Community / Forums / Process Mining / Start State or End sta...
Process Mining
Unanswered

Start State or End state missing

Posted on by 2

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:
  • LukasCervenan Profile Picture
    LukasCervenan 10 on at
    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 Profile Picture
    SudeepGhatakNZ 13,801 on at
    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 Profile Picture
    Russ_PowerLS 8 on at
    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

    1. One flow that tracks the start state ("Analysis") and measures the time spent in that state.
    2. 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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

September 2024 Newsletter…

September 2024 Community Newsletter…

Community Update Sept 16…

Power Platform Community Update…

Tuesday Tip #2 Global Search…

Welcome to a brand new series, Tuesday Tips…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 142,008

#2
RandyHayes Profile Picture

RandyHayes 76,308

#3
Pstork1 Profile Picture

Pstork1 63,531

Leaderboard