Skip to main content

Hi everyone,

I need an help: I want to indentify and calculate time between an activity 'A' and others that start with 'REC' (like image below)more_activities 

I'm able to identify the cases with PROCESS EQUALS:

 PROCESS EQUALS 'A' TO ANY TO LIKE 'REC%'

but I can use the function LIKE in CALC_THROUGHPUT

CALC_THROUGHPUT ( FIRST_OCCURRENCE E'A'] TO FIRST_OCCURRENCE E 'REC%' ] , REMAP_TIMESTAMPS("Activity"."timestamp", DAYS))

It gives me the warning "Target Activity "REC%" could not be found in the activity column and it doen't calculate the time.

Another use I would like to make of it, is to use it inside match_process_regex, like

MATCH_PROCESS_REGEX("Activity"."activity", 'A'>> 'REC%')

it gives me the same error of calc_throughput and it doesn't identify the right path.

 

How can I solve? How can insert the LIKE function in other functions?

 

Thanks

Hi Enrico,

 

you can do it as described here: Calculation / duration between a start and a list of possible events? (celopeers.com)

 

You can use REMAP_VALUES to change all REC related activities to one single value e.g.

 

 CALC_THROUGHPUT ( FIRST_OCCURRENCE R 'A' ] TO LAST_OCCURRENCE R 'B' ] , REMAP_TIMESTAMPS ("Activity"."timestamp", DAYS), REMAP_VALUES ( "Activity"."ACTIVITY_NAME" , q 'REC1' , 'B' ] , 3 'REC2' , 'B' ], # 'REC3' , 'B' ] ) )

 

BR

Dennis


Hi Dennnis,

thanks for you answer, but there are many REC activity (more than 20) and also they could increase over time dynamically.

I'm searching a quicker solution, as the LIKE function

 

 


Hi Enrico,

 

I am not aware of any possibility to make use of LIKE within CALC_THROUGHPUT, REMAP_VALUES etc.

 

BR

Dennis


I found by myself a solution that works and I am posting here to ask for confirmation of correctness and for the benefit of other users who have the same problem as me.

 

  • I created a saved formula that remaps all activities beginning with REC as “att_rec”

CASE WHEN "Activity"."activity" LIKE 'REC%'

THEN 'att_rec' ELSE "Activity"."activity" END

  • Then I inserted it into the calc_throughput formula

CALC_THROUGHPUT ( FIRST_OCCURRENCE E'A'] TO FIRST_OCCURRENCE E 'att_rec' ] , REMAP_TIMESTAMPS("Activity"."activity", DAYS), KPI("att_rec"))

 


Hi Enrico,

 

good idea which really seems to work.

Wasn't aware of the optional parameter for CALC_TROUGHPUT

CALC_THROUGHPUT ( begin_range_specifier TO end_range_specifier, timestamps , activity_table.string_column ] )

 

 

Thanks for posting and letting all of us know.

 

BR

Dennis


Reply