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.
I am in the process of identifying a attribute change in the account level not Identity level, and as for the information below is the link for this need
How ever it appears, it will identity after an aggregation as per above. but I would like to know attribute change at account level before the aggregation because the downstream system uses sailpoint API do update the data.
Can someone shed some light into this to identity account change for a specific attribute?
I don’t see any way that an attribute change can be identified before an account aggregation. That’s where SailPoint gets the updated data that indicates a change has been made.
@lalithajay Native account changes is for identifying what changed directly at the application end.
If the account attributes are synchronized to an identity attribute, then you can use the identity attributes changed trigger.
Otherwise, create the before/after rule to identify the changes and send alerts directly from the rule. I assume this option will be best fit for your requirement.
If you want to know more details, please let us know your use case/requirement little more in detail.
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.