In this post , I will show how ORCHPROCESS and ORCHEVENTS database tables can be used to know which out-of-the-box or custom event handler were triggered and what is their status.
It will help us in debugging if there is any issue with any event handler with respect to status, ordering or just in case we intend to turn off any event handler etc.
The Scenario that I executed to post the sample data is:-
Logged in with a test user and performed self change password operation.
First thing that we need is get the user key to start with
select usr_key from USR where usr_login= 'DDUBEY';
in my case the usr_key = 45 which will used as entityid in orchestration process table
After that use that in orchestration process table like below
Once you get that, we can use that id in orchestration events table like below
As you can see for 1 single operation there are lot of the out-of-the-box event handlers are getting fired for different stages like validation, preprocess action, audit and postprocess.
If you develop any custom event handler then you can see if its getting fired along with correct status and order that you like it to be along with other out-of-the-box event handlers.