Question
IP Australia
AU
Last activity: 6 Oct 2015 8:03 EDT
Date time selection from Calendar icon is updating with wrong values in clipboard in Pega 7.1.7
when we are trying to select datetime from calendar icon, the datetime on the clipboard is not getting converted to GMT. it is adding 4 hours to the selected (EST/IST) time.
Infosys
AU
Hi Mohammad,
From the clipboard screenshot it does seems that datetime value on clipboard has been converted to GMT. If I understand the issue correctly, you are not seeing the expected value in GMT. From the screenshot it seems the time zone of the system is "UTC -4:00"
Could you check the time zone setting/value on the system where you see this issue? Is it UTC -4:00?
Murali...
IP Australia
AU
Hi Murali,
Thank you for your reply... that time zone of the system i am using is "UTC-5.30". please see the screenshot. as i understand pega should convert this to -9 h 30 mins to convert it to GMT, that is not happening.moreover it is adding extra 4h to the selected value.
Thanks,
Mohammad Gouse Shaik.
Updated: 6 Oct 2015 8:03 EDT
Infosys
AU
Hi Mohammad,
I have tried changing my system's default time zone and yes it seems either a bug or extremely confusing behavior.
Original time zone of my Pega server is UTC +10:00.
My system's default time zone is also UTC +10:00. When I selected 14 Oct 2015 10:30 PM as date time value it got converted to correct GMT value of 20151014113000 GMT (note that my local time zone has day light savings now).
To test this scenario I have changed my system's time zone to UTC +5:30. Now when I selected 14 Oct 2015 5:00 PM as date time value it got converted to correct GMT value of 20151014060000 GMT. This means for user time shown in calendar gadget is as per user's timezone (5 PM UTC +5:30) but on the clipboard it is saved with same value but just changing the time zone of the server (5 PM UTC +10:00) and thus converting it to a wrong GMT value!!!
What is the pyDefaultTimeZone property value on Operator page (system page in clipboard)? What is the timezone of the Pega server location? If it is UTC -4:00 for your Pega server then we both are observing same behavior and this might be a bug!
Murali...