Skip to main content
Question

KPIs, components and filters

  • October 22, 2025
  • 1 reply
  • 21 views
Vladimir.Puskaric
Level 4
Forum|alt.badge.img

Hi,
I have a defined KPI in my knowledge model to calculate the median throughput time for my process:

 MEDIAN (CALC_THROUGHPUT (
    CASE_START
    TO
    CASE_END ,
    REMAP_TIMESTAMPS (
      "CONSUMER_APR_ACTIVITY_TABLE"."EVENT_DATE" ,
      DAYS
    )
  ))

I’d like to be able to compare median throughput times for all cases and only for cases which include a certain activity (for example: PENDING). I’d like to use either a table or a bar chart for this comparison.


What would be the best way to achieve that, considering that table filters apply on all columns? Can I introduce another KPI which will determine the median for cases which include PENDING only? If yes, how can I do that?
I look forward to receiving advice. Thanks.

Kind regards,

 

Vladimir

1 reply

manuel.wetze
Level 9
Forum|alt.badge.img+8
  • manuel.wetze
  • Level 9
  • 53 replies
  • October 29, 2025

Hi Vladimir,
I like your question. As you figured already your KM metric will well with filters which apply to different numbers. E.g. for KPI Lists you could use the Metric from the Knowledgemodel right away and just use different filters for both.

For your usecase to show both in one component with overarching filters I can think about two ways depending on which visual exactly you want to produce.

  1. You could add a new column as a dimension which essentially just flags if a case has Activity “PENDING” to it. You can achieve it with somehing similiar like 
    CASE WHEN PU_COUNT(case_table, activity_table.id, activity_table.name=’Pending’)>0 THEN ‘Has Pending Activity’ ELSE ‘no Pending Activity’ END. Or making use of the PROCESS EQUALS within the WHEN condition instead of a PU_COUNT. If this is a relevant and recurring question then I would add this as a calculated attribute to the Case record to be able to reuse it later.
  2. If 1 is not feasible you would have to create two different KPIs for Median Througputtime (one for all cases with and one for all cases without this activity. Again you would need to incorporate a CASE WHEN. But it would look something liket his  for the “Median Troughouttime for Cases with activity Pending”: MEDIAN( CASE WHEN ...(same conditions possible as stated in 1)…. THEN CALC TROUGHPUT (…. as you have above)           ELSE NULL END). Median does not consider NULL and therefore you can safely use it here.


Some thoughts of enhancements: if you want to dynamically change the name of the activity to be include you could think about using view variables for “PENDING” then you or maybe even the enduser could change the activity that should be included/excluded.




 


Community Code of ConductAccessibility statement