I must stress that working with time is always a major-bug source.
I have checked both GWD {Consumer,Terminal} API documentation, as well as the source code. Here is how our CMS handles the timezone. Again, I have already mentioned that in a previous email, but it is nevertheless important to make sure that we all understand how our CMS handles timezone.
- You can either send the time, in any
tranDateTime
parameter, asYYYY-MM-ddThh:mm[:ss]Z
, in this case, the time should be sent in UTC. This is what causes the +2:00 issue. In our CMS, we have set our timezone as Khartoum, which is UTC+2:00, so when we receive any request, we instantaneously convert it to the appropiriate timezone, the timezone that is recognized by EBS, which is UTC+2:00. All that depends on the fact that anytranDateTime
is received by CMS as UTC time. What we are doing now is sending our time in UTC+2:00! This is bug. It is neither from CMS, nor Alaa Aldin, nor EBS. - Or, we can send the `tranD