I have created a Customization Rule for AD application and it is working fine in dev environment but when it moves to QA, the rule is not getting executed.
Few of the things I have tried to debug but it did not work:
Tried to print logs
Throw an exception
Execute account aggregation with partition and without partition.
Checked disabled optimization option on account aggregation task.
Customization rule is not getting executed for existing AD application and rule is executed for newly created AD application which means there is something issue with existing AD application.
yes, I did try by just return null but aggregation is successful and I can see all object are coming into SailPoint. This means customization rule is not even executed in aggregation
That is very weird. Can you tripple-check that you’re aggregating from the correct application? Maybe add your rule to another application and see the result from there?
yes this is unusual. I had config the same rule to newly created AD application and rule is getting executed but for existing AD application its not getting executed.
and also configured for existing azure ad application and rule is getting executed
Can you try doing a preview from the schema page? That should also execute the customization rule, ruling out the something is wrong with the aggregation task.
I think customization rule will only trigger for the object when a change has occurred. So try updating some attribute in AD for that object and run your aggregation again.