Hi all. We have created 6 activity tables, and allowed the data model to create a merged activity table. When I add the Case explorer component, it isn't using the merged activity table, but defaulting to one of the 6 we've created. Also, for the conformance component, I've allowed celonis to mine, and this too is defaulting to the same activity table. Do any of you know how to get these two components to use the merged activity table?
Hi all.
+10Hi Julie,
when you use the multi-event log, you have to define a default activity table. This is the one that is used by all the components unless you can customize the dimension (like in the variant or process explorer components since a couple of months). Others like Conformance or Case Explorer dont' have that customization yet.
I have created a request for the Case Explorer component some time ago and should have a call this week to present it. But it definitely is relevant for all components in the same situation. I'll see if the subject of my request can be extended or if a new one is necessary.
regards
Marc
Hi @julie.harmo11 , hi @marc.rilla12 ,
we made a change that in case you use the "automerge eventlog" function in the data model, that the automerged event log (_CEL_MERGED_ACTIVITIES) will be considered as the default eventlog for the analysis.
We already released this for the analysis inside "Process Analytics", and we are going to release it as well for the analysis inside "Studio" this week.
I hope this will help for your use case Julie, to leverage the merged activity table for components like the Case Explorer, Conformance Checker etc.
All the best
Sabeth
+10@sabeth.stein that is wonderful news! We ended up creating our own merged event log and made that the default event log.
Glad you found a workaround and happy that we can solve this better for upcoming implementations! :)
Hi @julie.harmo11 , hi @marc.rilla12 ,
we made a change that in case you use the "automerge eventlog" function in the data model, that the automerged event log (_CEL_MERGED_ACTIVITIES) will be considered as the default eventlog for the analysis.
We already released this for the analysis inside "Process Analytics", and we are going to release it as well for the analysis inside "Studio" this week.
I hope this will help for your use case Julie, to leverage the merged activity table for components like the Case Explorer, Conformance Checker etc.
All the best
Sabeth
thanks for the update, this enhancement will be highly appreciated.
regards
Marc
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.