I see incorrect date in my Jasper Report / IM GUI for User Creation Date, Last Modified Date or Last Login Date attributes.
Article ID: 281390
Updated On:
Products
CA Identity Suite
CA Identity Manager
Issue/Introduction
I see incorrect date in my Jasper Report / IM GUI for User Creation Date, Last Modified Date or Last Login Date attributes.
Options:
1. In IM UI you see date starting with 17XX XX XX using Logical Attribute Handler with DateDisplayHandler
2. In Jasper Report or imruser6 table in Database you see date 26XX-XX-XX YY:YY:YY
Instead of normal date 2024-XX-XX
Options:
1. In IM UI you see date starting with 17XX XX XX using Logical Attribute Handler with DateDisplayHandler
2. In Jasper Report or imruser6 table in Database you see date 26XX-XX-XX YY:YY:YY
Instead of normal date 2024-XX-XX
Environment
Identity Manager 14.X
Cause
Reports snapshot function expects User Creation Date, Last Modified Date or Last Login Date attributes to be provided as Unix time (ex. 1710241525).
This format read by LAH will cause issue 1.
Logical Attribute Handler - DateDisplayHandler expects User Creation Date, Last Modified Date or Last Login Date attributes to be provided as simpleDate format (ex. 20240329121212). It will also save these attributes as such if provided in User Defined format. This format snapshotted and viewed in Jasper report will cause issue 2.
This format read by LAH will cause issue 1.
Logical Attribute Handler - DateDisplayHandler expects User Creation Date, Last Modified Date or Last Login Date attributes to be provided as simpleDate format (ex. 20240329121212). It will also save these attributes as such if provided in User Defined format. This format snapshotted and viewed in Jasper report will cause issue 2.
Resolution
Either create custom attribute to store dates in your preferred format, or create custom LAH to handle UNIX time in GUI.
Additional Information
Reports should support handle different date formats from 14.5.2.
Feedback
Yes
No
Powered by
