I’m facing a challenge with syncing an attribute within a Web Service Source.
I’ve written a Cloud Attribute Generator Rule that looks up an identity’s manager and then fetches the PhoneNumber Attribute from the manager’s account on the same web service source. Here is a snippet of code of this Rule :
This rule is designed to populate a target attribute that is PhoneNumberManager.
The rule works perfectly during the initial account creation . However, it does not automatically re-trigger if the manager of an Identity changes.. I don’t know how to trigger the rule for this case.
Since the manager’s PhoneNumber is an account attribute and not an identity attribute changes to it do not seem to trigger the generator rule.
How can I ensure this Attribute Generator Rule re-executes whenever the identity’s manager changes ? Is there a workaround to keep this attribute in sync? I cant add the managerPhoneNumber as an Identity Attribute..
As far as I understood you would like to re-trigger attribute sync for webservice source whenever Identity manager’s change and sync manager phoneNumber from the webservice manager account link.
You can achieve it by event-driven workflow. Below are the suggested steps to follow the same:
Create Identity change attribute workflow
Set trigger as Identity attribute change
Choose filter on the specific attribute. In your case it would be manager field.
Add a sync API step which calls SailPoint API to synchronize attributes.
Could you please let me know why you want to re-trigger the rule which is configured in “Create Account Policy”. As attribute sync will only sync Identity attributes in case it match un-matches value on the target end. But purposely if you want to trigger sync again you can use the below provide API - synchronize-attributes-for-identity | SailPoint Developer Community
Why can’t you create an Identity Attribute with the manager’s phone number? That would be a very straightforward solution, but instead you’re developing a highly custom work-around. I’d recommend pushing back on this “requirement”.