Skip to Content

Agency Client's Time Doesn't Match Windows Time

When the user changes the time zone of the Window's OS, while logged into the Agentry client application, then the timestamp of transaction.timestamp pulls the previous time zone and it's associated time. E.g 2PM EDST changed to CDST and sent transaction at 1:05 CDST shows up as 14:05 -4:00 (we're using the time zone difference to GMT), when it should show 13:05 -5:00. A transmit will update the time zone difference properly from a -4:00 to -5:00, but will not update the time from 14:05.

The only known way to update the time properly after a time zone change initiated by the user in Win7 is by logging out of the Agentry client app a and logging back into the client app. This will fix both the time and time zone issue mentioned above. Appears the time zone is cached between transmissions and the time is pulling from a system variable not subject to

Is this a known SAP issue on WPF? Does this perform similar on iPad devices?

Client version: 70.7.1

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Apr 25, 2017 at 01:47 PM

    Hi Brad,

    We can configure time zone setting in SMP.Please find the below link for further details.



    Add comment
    10|10000 characters needed characters exceeded