Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
Context :
We have updated the Manager Correlation Rule attached recently to compute the new manager based on specific criteria (lifecycle state, grouping and sector attributes).
Since there is no change on the ADP (SIRH) authoritative source, we tried to execute an unoptimized aggregation on that source, but effectively the manager has not been re-evaluated and some identities are still attached to the wrong manager in ISC.
Question :
Is there any capability to re-evaluate the Manager Correlation Rule while running an aggregation without asking for changes on the authoritative source of identities ?
I believe a refresh of the identity should force the manager correlation rule to re-run. You can do this on the identity object → Actions → Process Identity or through the API - start-identity-processing | SailPoint Developer Community
If this doesn’t resolve, its likely due to some issue with the rule logic or the manager identity that its being mapped to. If there is an error when correlating to the new manager, ISC will keep the existing manager. Could you validate there are no errors on the manager identity and that your correlation rule is working as expected.
If the issue is only happening to a specific set of identities, leaning towards this being an issue with the manager identities rather than rule logic.
I did process the identity and also tried an unoptimized aggregation without any success.
I did simplified the code to simulate it in a compiler and the identity effectively goes into the right condition and if / else block that should return the target identity.
Will try to re-work the rule and check for any additional case.
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.