pxCommitDateTime and pxUpdateDateTime differs by 4 hours
Hi All,
We are having an issue where the pxUpdateDateTIme and pxCommitDateTime values are not matching.
Scenario-
Case raised at 11:39 AM. Case resolved completed at 11:44 AM.
pxUpdateDateTime is 20200822T154438.672 GMT is in line with the time when the case was resolved i.e 11:44 AM Eastern time.
Whereas the pxCommitDateTime is 20200822T194413.677 GMT which is in the future at the time case was resolved. 19:44 GMT translates to 3:44 PM Eastern which is in the future when compared with the time case being resolved.
Any ideas will be appreciated.
Regards
Bidyun
Accepted Solution
Updated: 25 Aug 2020 7:53 EDT
Pegasystems Inc.
US
Are the database server and application servers configured to use the same time zone?
Scotiabank
CA
Thank you so much for the very helpful update Carissa!
I have reached out to the network team and requested them to check.
Will update this thread.
Regards
Bidyun
LTIMindtree
CA
Hi Carissa,
Just wanted to mention that even though syncing the time-zones resolved the pxCommitDateTime diff with pxUpdateDateTime issue, it gave rise to a situation where the audit time logs on the case history is not being displayed according to the Operator ID locale/timezone settings. Its always defaulting to GMT and not taking the operator IDs settings.
Are we missing any other steps that need to be taken after this synchronization?
Regards
Bidyun
Pegasystems Inc.
US
Is this occurring for entries created before or after the time synchronization? What section is being used for the audit history display?