Looking through the forum I can see that the date-compare transform’s “now” keyword is in UTC (great, I expected that).
If we are performing calculations against values on a source that come in as EST/EDT, how do we correctly observe daylight savings time in the transform.
The hacks using static shifts (e.g., +11 hours) obviously do not observe DST.
Is a BeanShell based transform the only way to incorporate DST aware datetime calculations in SailPoint?
Hey @josephcasale !
I very strongly agree with you that this is a big shortcoming of the way the transform primitives handle dates. I literally just mentioned this to a customer earlier today!
I recently asked about getting the Velocity dateTool added to static transforms, since it’s already supported in SailPoint’s email templates. @tyler_mairose mentioned he’d talk to the folks responsible for transforms about it, hopefully we’ll be able to get some traction there.
In the meantime, I’ve been inspired by your post and have submitted my request to the Ideas portal for better tracking and visibility. Please go and add an upvote!
Hi @sup3rmark ,
Thank you for all that effort!
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.