Question

Save As Circumstance Date with TimeZone

We are working to upgrade pega from Pega 6.3 SP1 to Pega 7.3.1. We use Circumstance Date very often for our DecisionTable, MapValue and When Rule. Since Pega 4.2, we set the Circumstance date in the format "20190501T000000.000 GMT", but in Pega 7.3.1, we have this validation error : "20190501T000000.000 GMT is not a valid date/time value". Do we have a way to change this validation or to force the GMT timezone for all users. Because, if I use the interface, it saves it in my timeZone (East -4/-5) and the interface doesn't allow to change the timezone.

Comments

Keep up to date on this post and subscribe to comments

May 2, 2019 - 3:10pm

Any news about this problem ?

June 17, 2019 - 8:44am

There is the answer from Pega :
"Customer was relaying on a bug, validation for DateTime was not their in previous releases. As Designer studio has updated the validations, now it is failing for customer. But it was never expected for RuleResolution to get timeZone. 

Customer should handle converting time to server timezone themselves."

 

Our question : "How can we do that?"

Their second answer :
"Hi ,You can try that in our end.You need to do it in your end"

 

So, Pega doesn't support the format they use to keep all their dateTime anymore.