Hi.
Our OIM 9.1.1 instance is integrated with our HR system for identity and organizational data. For organizational data, we also get the manager value from HR. In OIM, we use the manager value from department as manager value for identity objects (solved through template on Person.UID_PersonHead). This works well in most cases, but in some cases, we're getting circular nesting error during synchronization of HR data. This is due to discrepancy between how manager data can be registered in HR and rules for managers in OIM (more specifically, formatting script for Person.UID_PersonHead). The result is that we have a certain number of departments and users without manager in OIM.
Unfortunately, we can't change the way HR data is registered. These situations can arise at different organizational hierarchy levels, so there are no workaround-rules that we can implement during HR synchronization to mitigate this issue. Since we need manager data on department and identity objects for notifications etc., we're considering removing the rules for circular nesting in OIM. We know that this may cause issues with approval and attestation workflows (not currently used). This is maybe something that can be solved through customized workflows. But we would like to know if there are any other potential issues that can arise if we remove the rules for manager circular nesting in OIM. Does anybody have experience with this?
Br,
Tin