Hi @mayamis1703eq
Have you defined manager correlation for the HRMS application as well as mapped the manager mapping in identity attributes.
If yes please share more information to be able to help you
Hi @pradeep1602 : I have done both.
@mayamis1703eq
Can you share your configuration, a dialouge does not really help determine the issue
Hi @pradeep1602 : The issue i am facing is while the manager changes , the values do not update in identity. other wise it is working properly. Thank you!
Is the new manager value getting updated in the auth source link in SailPoint?
If it is updated in the link then make sure that you run the Identity Refresh with Refresh Identity Attributes and Refresh manager status, option selected.
hi @mayamis1703eq Can you share your Manager attribute identity mappings > Mainly the Edit mode information?
Hi @msingh900 : New manager is coming as null but still old value is showing
Yes, this is expected if Manager attribute is read‑only in Edit Mode.
You have a few valid ways to handle this, depending on the desired behavior:
Option 1: Make the attribute editable permanently
If you want the Manager value to remain as manually set and not be overridden by refresh or source data, mark the attribute as Editable and remove/disable any correlation logic. This makes the identity value authoritative.
Option 2: Use a Value Change Rule (recommended)
Implement a Value Change Rule (or adjust the managerCorrelationRule) to control when the Manager value should be recalculated. This allows you to:
Respect manual changes when needed
Fall back to source/correlation logic otherwise
This is the safest and most flexible approach.
Option 3: Rely only on the source (best long-term)
Keep the Manager attribute read‑only and ensure the correct value is coming from the authoritative source or correlation attributes. Manual edits should not be expected in this model.
Hi @haideralishaik : I didn’t understood.
Read only means value will be updated on next aggregation, right?
So manager should be set to blank automatically.
Please elaborate if i am not getting it right
@mayamis1703eq Got it — let me simplify this.
Read‑only does NOT mean IIQ will clear the value automatically.
It only means you cannot edit it from the Identity UI. The value will be set only when aggregation or identity refresh provides a manager value from source / correlation logic.
So:
If the source sends a manager → IIQ updates it
If the source sends nothing → IIQ keeps the last calculated value (it won’t blank it by itself)
That’s why you’re seeing “unexpected” values.
If you want:
Manual value to stick regardless of source → use Edit Mode = Permanent
Manual value temporarily, but allow source to overwrite later → Temporary
Fully source‑driven behavior (recommended) → keep Read‑only and ensure the authoritative source or manager correlation is correct
In short: manager won’t auto‑blank just because it’s read‑only — it only changes when a refresh supplies a value.
Hope this clarifies it 
Hi @haideralishaik : Then what should i do if i want to update it to null if the value coming from Source for Manager is Null
@mayamis1703eq
If you want Manager to be cleared when the source value is null, you have two practical options:
Option 1 (Recommended): Update the correlation logic
Modify the managerCorrelationRule (or related refresh logic) so that:
Option 2: Value Change Rule
Add a Value Change Rule on the Manager attribute to detect when the source value is null and explicitly set the identity attribute to null.
Keeping it Read‑only alone is not enough — read‑only only blocks UI edits; it doesn’t auto‑clear values.
Summary:
To set Manager to null, the refresh logic or rule must explicitly do it.
Hope that clears it up
Should i write the logic in “manager Correlation rule” on application level OR in Identity Source mapping of Manager attribute.
Please suggest
I would prefer "managerCorrelationRule "
The managerCorrelationRule is explicitly designed to derive, override, or clear the Manager value during Identity Refresh.
That’s the only reliable way to ensure Manager is cleared when the source has no value.
@mayamis1703eq There is no need of Manager Correlation Rule to update Manager Attributes. How are you updating the manager attribute? Is it directly done in Debug under HR app link or you are updating it via UI or via some rules?
Also, check after making change and running tasks, check it in debug as well. Sometimes it gets updated in DB and at identity level but UI still showing old values due to cache.
Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(
,, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.
Hi @mayamis1703eq ,
There are many customizations available in IIQ. Just want to add few points as best / recommended practice -
Manager value is expected to come from HR (authoritative) application(s)
Identity attribute for manager should be “Read only”
Manager correlation rule should be used only if it is necessary. If mapping is simple then attribute based configuration is recommended. Same thing for “Value Change Rule”
In most cases, manager value is not empty in authoritative applications. You can decide how to handle if manager value is not provided in HR app based on your project requirement and policies.
Hi @haideralishaik : I got it working now.
Just FYI, “Manager Correlation Rule” was not working when Manager value comes NULL from HR source.
I wrote the logic in “Manager Identity Mapping rule” because we can catch the NULL event here only.
“Manager Correlation Rule” will NOT receive this NULL event.
Thanks for you help!
