Hi @vaibhav_dubey_yancoal ,
I want to understand the use case for which you are trying to do this…!!
are you trying to compare the “created” timestamp with now date, and deciding if the user is “working” or “not working” in organization ?
If yes then even if you get the transform right, you will always get user as “working”. So, I fail to understand the point of building this transform.
Could you please tell what is the use case and what exactly are you trying to solve/achieve ?
I can suggest you a way here, you can get the startDate of an identity using accountAttribute and can compare with the current date (now). By this way, you can achieve the employee is in working state or not.
(I will not suggest you to go with IdentityAttribute for this case, as IdentityAttribute creation is a multi-threaded process. As a best-practice, you can use accountAttributes, wherever if possible, when the identity enters into IDN via Auth. Source)
Created timestamp will give you the time and date, which the identity created in ISC.
If you have terminated the person too, it will show the created date.
And also, the above given suggestion selects only for prehire and active condition, not for inactive/terminated.
But I think on the first go, when an identity is created, this created attribute might not get any value I think so when this transform get executed. But on the second go, you can see the result.
Understood,
I think you are not getting any value when you are using identityAttribute transform for getting “created” value,
I would check this with SailPoint Support and see what they suggest.