Question
virtusa technologies india pvt ltd
IN
Last activity: 16 Oct 2018 12:03 EDT
DateTimeFormat Is Incorrect after Upgrade
Hello,
Problem:
The value of ReturnedDate should hold time zone specific date time value in equivalent GMT format. This behavior was working in Pega version 6 and not in Version 7.
Properties Used:
1. LDate Date data type
2. Returned Date Date Time data type
Logic Used In Activity: In this step property-set method is used
PropertiesName PropertiesValue
Param.LDate @date(Param.Year,Param.Month,Param.Day)
Param.ReturnedDate Param.LDate
Note: The current operator is mapped with America/New_York time zone and calendar is US Default
Steps to reproduce Issue:
Scenario in Pega 6:
when I tested the above scenario in pega version 6,I can see datetimeformat as shown below
Input : 01012017
Output: 01012017T050000.000 GMT
Scenario in Pega 7:
when I tested the above scenario in pega version 7,I can see datetimeformat as shown below
Input : 01012017
Output: 01012017T000000.000 GMT
Can anyone advice how we can achieve this problem in pega 7 version.
ThanksInAdvance
**Moderation Team has archived post**
Hello,
Problem:
The value of ReturnedDate should hold time zone specific date time value in equivalent GMT format. This behavior was working in Pega version 6 and not in Version 7.
Properties Used:
1. LDate Date data type
2. Returned Date Date Time data type
Logic Used In Activity: In this step property-set method is used
PropertiesName PropertiesValue
Param.LDate @date(Param.Year,Param.Month,Param.Day)
Param.ReturnedDate Param.LDate
Note: The current operator is mapped with America/New_York time zone and calendar is US Default
Steps to reproduce Issue:
Scenario in Pega 6:
when I tested the above scenario in pega version 6,I can see datetimeformat as shown below
Input : 01012017
Output: 01012017T050000.000 GMT
Scenario in Pega 7:
when I tested the above scenario in pega version 7,I can see datetimeformat as shown below
Input : 01012017
Output: 01012017T000000.000 GMT
Can anyone advice how we can achieve this problem in pega 7 version.
ThanksInAdvance
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
IN
Hi Srinivas,
Thank you for posting on PSC. This post looks like its related to your earlier post: DateTime Format in GMT is Incorrect after upgrade
Do you wish to continue on just one of your posts to avoid confusing the other community members? Can I close your earlier post?
Regards,
virtusa technologies india pvt ltd
IN
Hi Lochan,
I Have explained same scenario in business terms which will be helpful to understand my requirement problem asap
Pegasystems Inc.
IN
Hello!
Thank you for the reply. I have marked the older post as closed and linked the 2 posts so that the discussion is focussed on just 1 thread.
Regards,
The Toronto-Dominion Bank
CA
Hi Srinivas,
Is this issue resolved? We have a similar issue after upgrade to Pega7.
Please let us know if you found a resolution for the same.
Thanks
Pegasystems Inc.
IN
Hello Himabindu,
Thanks for posting your query in PSC :)
As per the reported behavior, in PRPC 6.x ,when Date property is assigned to a DateTime property the difference of time zones is appending to DateTime property which is not the expected behavior. Ideally, it should append T000000.000 GMT value to the Date value as observed in version Pega 7. This is expected behavior.
If you observe a time difference, in a Data Transform, add the time difference which is equal to amount of time between operator timezone and GMT.
For example: 5.30 hours is the difference between IST and GMT. Add 5 hours 30 minutes to selected time before assigning it to Date property.
@(Pega-RULES:DateTime).addToDate(Param.DateField, 0, 5, 30, 0)
I hope this helps.
Regards,
Rincy
The Toronto-Dominion Bank
CA
Hi Rincy,
Thanks for your response.
The workaround suggested will work in this scenario, but the daylightsavings time duration needs to be taken into consideration for EST timezone. But also the issue is that, even in Pega6, the Datetime property value has a timestamp of T000000.000 GMT which is the same in Pega7 . But somehow, when it comes to the UI, in Pega 6 the correct Date is displayed, but in Pega7 the date is always 1 day behind due to the GMT-EST conversion and with the same Operator Timezone/Calendar values in both Pega6 and 7.
Any clue on why the GMT-EST conversion is not happening in Pega6, even though the Datetime value is with timestamp of T000000.000 GMT.
Pegasystems Inc.
IN
Hello Himabindu,
Could you confirm the PRPC 6 version and provide the hotfix inventory from this application.
Regards,
Rincy