We've encountered a few issues where the local / corporate time zone is not being applied correctly or consistently in landmark lists and filters. These issues can lead to a misrepresentation of data or undesired / incorrect data being returned when landmark filters are applied in lists and process flows. This affects any business class that has a create date field, and possibly other TimeStamp / Date fields as well.
If you agree that the that the time zone should be reflected accurately and consistently, I'd appreciate your endorsement on the enhancement requests below.
Thanks!
Andy
ER81810 - Landmark filters return incorrect data - Does not apply time zones to TimeStamp date fields
ER81801 - Apply local time zone to "time" TimeStamp Operator
