Hi All,
At my current client, we read the HR data in the form of a file extract and use it for account provisioning and deprovisioning. In particular, the deprovisioning activity is triggered by the employee end date attribute which is supplied in the HR extract - when this end date passes the user object is disabled and moved to the disabled users OU. Further, we also flow this to the accountExpires AD attribute (coded a RE do to that)
Now, the IT team have requested that they be able to overwrite this end date in the portal since sometimes the end dates in HR are incorrect, leading to disabling active users. We initially got around this by setting this attribute to equal precedence between the HR extract and the FIM portal (I know equal precedence is being deprecated in future releases, but thats a separate topic of discussion). Now this works fine, except that when we do a full import + full sync on the HR extract (once a day on a task schedule), it overrides the end date in the Portal with the HR data and the IT team have do again go an re-enable this account. They are looking for an option to permanently override the end date unitl it changes in the HR extract, in which case the HR extract date should be used.
IF we use delta syncs all the time then this is fine and the last value changed will be the one used, however when we do a full sync on the HR MA then that value always overrides the FIM value. I tried to do a RE for this by trying to query the HR connector space object for the user to see when was the last modification time stamp of this attribute and if it is greater than the one in the metaverse then flow it in, however I cannot query the timestamp of the attributes in the CS.
Any suggestions on how to best go about this?
Thanks in advance and sorry for the long post!