Support Article
Date Time Property Issue is adjusted 5 hrs despite BST TimeZone.
SA-12164
Summary
PRPC 7.1.7. ( operators and servers across many time zones ) User's operator Time Zone is set to the GMT.
Date Time from Connect SOAP Date Time value in PEGA
2014-03-27T10:30:35Z 27/03/2014 10:30
2015-06-24T15:33:52+01:00 24/06/2015 14:33
As user traced through, as soon as the parsing happened the date value is changed even before any transformation.
Changing to BST does not work - the time deviates by 5hrs.
In the operator profile the setting is in GMT.
The interface response sends the right value but is modified during parsing.
If I use European/London it works fine.
Error Messages
N/A
Steps to Reproduce
Call The interface and check the loaded data page.
Root Cause
The root cause of this problem is defect/misconfiguration in the operating environment. BST is not a valid Timezone for correct GMT adjustment.
Resolution
The explanation for this behavior is as follows: the operator needs to be assigned a timezone value which will be adjusted to BST, such as Europe/London. GMT is an absolute timezone and does not get so adjusted.
Published July 14, 2015 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.