Thu, 27 Feb 2014 05:34:35 +0000Added tag 3.0MP31.2 for changeset 3044ba5dda0c
RM packaging bot <staff.rm@openbravo.com> [Thu, 27 Feb 2014 05:34:35 +0000] rev 22281
Added tag 3.0MP31.2 for changeset 3044ba5dda0c

Thu, 27 Feb 2014 05:34:35 +0000Update AD_MODULE version to 3.0MP31.2 3.0MP31.2
RM packaging bot <staff.rm@openbravo.com> [Thu, 27 Feb 2014 05:34:35 +0000] rev 22280
Update AD_MODULE version to 3.0MP31.2

Wed, 26 Feb 2014 13:33:41 +0100fixed bug 25832: Problem with the status of process requests
Asier Lostalé <asier.lostale@openbravo.com> [Wed, 26 Feb 2014 13:33:41 +0100] rev 22279
fixed bug 25832: Problem with the status of process requests

Wed, 26 Feb 2014 10:51:11 +0100Related to issue 25838:Avoids accessing a property of an undefined object
Augusto Mauch <augusto.mauch@openbravo.com> [Wed, 26 Feb 2014 10:51:11 +0100] rev 22278
Related to issue 25838:Avoids accessing a property of an undefined object

The check (if data[this.name]) to avoid accessing a property of data[this.name], that can be undefined, has been moved from here

if (this.getValue() !== data[this.name]) {

to here

data[this.name].getFullYear() <= 1970)

It did not make sense to make the check in the outer if clause, because that would disable setting a null value for this property from the datasource.

Wed, 26 Feb 2014 10:20:31 +0100Related to issue 25838:Avoids accessing a property of an undefined object
Augusto Mauch <augusto.mauch@openbravo.com> [Wed, 26 Feb 2014 10:20:31 +0100] rev 22277
Related to issue 25838:Avoids accessing a property of an undefined object

Wed, 26 Feb 2014 10:05:46 +0100Fixes issue 25838: Time fields work properly in timezones with negative offsets
Augusto Mauch <augusto.mauch@openbravo.com> [Wed, 26 Feb 2014 10:05:46 +0100] rev 22276
Fixes issue 25838: Time fields work properly in timezones with negative offsets

There was a problem the todays date was assigned to a datetime:

Original date: 31/12/2013 10:00:00
Todays date: 25/02/2014

The assignment order was year, month day, so the datetime was transformed like this:
Year updated: 31/12/2014 10:00:00
Month updated: 31/02/2014 does not exists, so it is converted to 03/03/2014
Day updated: 25/03/2014

This has been fixed by changing the updating order to Day, Month, Year. Before the update the date month is set to January to prevent setting a day not supported by the current month.

Tue, 25 Feb 2014 11:21:33 +0100Fixes issue 25827: Time fields work properly in timezones with negative offsets
Augusto Mauch <augusto.mauch@openbravo.com> [Tue, 25 Feb 2014 11:21:33 +0100] rev 22275
Fixes issue 25827: Time fields work properly in timezones with negative offsets

Depending on who calls the formSaved function of OBTimeItem, the provided time can be already converted to the client local time or not. To know the time has a
lready been converted, the function used to check if the full year of the time was 1970. If that was the case, then the time was converted from UTC to local ti
me.

The problem is that if the user is working from a timezone with negative offset the full year will not be 1970, but 1969. This has been fixed by replacing data
[this.name].getFullYear() === 1970 with data[this.name].getFullYear() <= 1970

Fri, 21 Feb 2014 00:46:21 +0530Fixes Issue 0025781: download all attachments fail
Shankar Balachandran <shankar.balachandran@openbravo.com> [Fri, 21 Feb 2014 00:46:21 +0530] rev 22274
Fixes Issue 0025781: download all attachments fail

When downloading all attachments older method of retrieving attachments was always used.
Called the appropriate method to determine the attachment model and download accordingly.

Fri, 24 Jan 2014 14:30:20 +0530Fixes Issue 25511:WrongMatchInvAccounting modulescript alertrule performance
Atul Gaware <atul.gaware@openbravo.com> [Fri, 24 Jan 2014 14:30:20 +0530] rev 22273
Fixes Issue 25511:WrongMatchInvAccounting modulescript alertrule performance

Fri, 21 Feb 2014 08:56:43 +0100related to issue 25773: added test cases to cover the issue using XML and JSON
Asier Lostalé <asier.lostale@openbravo.com> [Fri, 21 Feb 2014 08:56:43 +0100] rev 22272
related to issue 25773: added test cases to cover the issue using XML and JSON