Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0020751Openbravo ERPA. Platformpublic2012-06-13 16:162012-06-18 16:45
AugustoMauch 
AugustoMauch 
immediateminorN/A
closedfixed 
5
 
3.0MP133.0MP13 
Core
No
0020751: API change: time fields are sent in UTC
The changeset https://code.openbravo.com/erp/devel/pi/rev/976c8398def2e80de470ab55db222555d88566d8, [^] which fixes issue 20684, has modified the way time fields are sent from the server to the client and vice versa.

To be able to support time fields with differente time zones, they have to be sent in UTC, and converted to local time upon being received.

This fields used to be sent using the local time of the sender.
There may be clients that are receiving time fields from the server, and expect them to be in the server's local time. Now they will receive UTC times, and are expected to send UTC times too.
No tags attached.
related to defect 0020684 closed AugustoMauch Incorrect time in process request with different timezones in client/server 
Issue History
2012-06-13 16:16AugustoMauchNew Issue
2012-06-13 16:16AugustoMauchAssigned To => AugustoMauch
2012-06-13 16:16AugustoMauchModules => Core
2012-06-13 16:17AugustoMauchRelationship addedrelated to 0020684
2012-06-13 16:18AugustoMauchAssigned ToAugustoMauch => iciordia
2012-06-15 13:28iciordiaNote Added: 0049853
2012-06-15 13:28iciordiaAssigned Toiciordia => AugustoMauch
2012-06-15 13:33AugustoMauchNote Added: 0049855
2012-06-18 16:41AugustoMauchStatusnew => scheduled
2012-06-18 16:41AugustoMauchfix_in_branch => pi
2012-06-18 16:45AugustoMauchStatusscheduled => resolved
2012-06-18 16:45AugustoMauchFixed in Version => 3.0MP13
2012-06-18 16:45AugustoMauchFixed in SCM revision => https://code.openbravo.com/erp/devel/pi/rev/976c8398def2e80de470ab55db222555d88566d8 [^]
2012-06-18 16:45AugustoMauchResolutionopen => fixed
2012-06-18 16:45AugustoMauchStatusresolved => closed

Notes
(0049853)
iciordia   
2012-06-15 13:28   
Approved.

Ismael
(0049855)
AugustoMauch   
2012-06-15 13:33   
Risk assessment:

This change may only affect negatively those who receive a time from the server and parse it to a date with a non-standard function. In that case, the problem will be solved if the non-standard function is changed to support the lack of GMT offset.