How can I connect Process Adherence Manager results to an Action Flow in Celonis?

Hi Christina, 
This seems to be to vague of a requirement to have a simple answer. As to the best of my knowledge there is no direct integration between PAM and Action Flows. So here is how I would tackle it:

Firstly I advice to be very specific on when exactly do you want to be alerted? aka when should a given action flow be triggered. If one case violate the target model? If more than 30 cases violate the target model? Or if conforming cases in total drop below 10%? You see there might be many different interpretations on “trigger alerts on deviations”.

If you gained clarity on that I would define PQL metrics on the exact conditions you want to be alterted for.

e.g. >30 cases with undesired activity a, or without a mandatory activity, or with wrong order of activities.

Lastly: you can set up one or more Action Flows.
Those PQLs can then be used to query and start an action flow.
I would setup an action flow to check e.g. once a day and filter based on any of the defined conditions are violated, then send e.g. an email. 

 

Hi Manuel, Thank you for your response. My goal is to receive a notification whenever something deviates from my target process. I’ve already written a PQL code using BPMN_Conforms to apply it as a filter so that I can exclude all non-conforming cases. This works so far, but all cases that are not yet completed are considered non-conforming by BPMN_Conforms.

Is there a way to treat ongoing cases that are not yet finished as conforming, as long as the sequence so far is correct? I’ve already tried several variations, but none of them worked.

Is it a must requirement to get alerts for cases “in progress” as soon as they deviate? Does the rest of the backend (extractions, transformation) supports near real time alerting aka. getting fresh data within minutes after an activity was executed in Production system?

I normally define one or more “end activities” of the Process and consider only cases which have one of those activities present for exactly the reason to not have incomplete variants in the logs.

If you do need to produce alerts for in progress cases you can take the same approach but increase granularity. Essentially cut the process in half: Check if the middle activity is present → then compare to the Should process definition for the first half. Check if the end activity is present → then compare to the definition of the whole process. You can follow the appraoch and increase granularity as much as needed e.g. cutting it in 4 parts and so on. But this is tidious work to maintain and set up, so I would prefer 1st approach if possible.