Wed, 10 Jun 2015 16:55:01 +0200Fixes issue 30139: Error when generating credit and adding a negative line
Alvaro Ferraz <alvaro.ferraz@openbravo.com> [Wed, 10 Jun 2015 16:55:01 +0200] rev 26994
Fixes issue 30139: Error when generating credit and adding a negative line

Add Payment was raising an error if credit used was greater than total amount.
Now, this comprobation will only be done if some record has been selected in Credit To Use grid.

Wed, 10 Jun 2015 17:14:48 +0200Fixes issue 30113: Critical bug with decimals only in PostgreSQL 9.3
Carlos Aristu <carlos.aristu@openbravo.com> [Wed, 10 Jun 2015 17:14:48 +0200] rev 26993
Fixes issue 30113: Critical bug with decimals only in PostgreSQL 9.3

A new build validation has been added. This way, when executing update.database the result returned by the to_number() procedure is evaluated.
In case it does not return the expected result, the task will fail, showing a message with the link to the documentation.

Wed, 10 Jun 2015 10:22:04 +0200Fixes issue 30090: Select Payments Pick&Edit window is not working properly
Carlos Aristu <carlos.aristu@openbravo.com> [Wed, 10 Jun 2015 10:22:04 +0200] rev 26992
Fixes issue 30090: Select Payments Pick&Edit window is not working properly

When selecting a record in a P&E grid, the request done to the FIC was not using the correct mode. Now, when selecting a record, the request is properly done using the EDIT mode.

Thu, 04 Jun 2015 17:47:14 +0200Fixes issue 30098: BP current balance not properly updated
Alvaro Ferraz <alvaro.ferraz@openbravo.com> [Thu, 04 Jun 2015 17:47:14 +0200] rev 26991
Fixes issue 30098: BP current balance not properly updated

Change condition in FIN_PaymentProcess to take into account when the paymend does not have order nor invoice related (when it only has a g/l item, when we are genereting credit or when we are refunding amount).

Thu, 04 Jun 2015 17:02:09 +0200Related to issue 30104: updated copyright
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Thu, 04 Jun 2015 17:02:09 +0200] rev 26990
Related to issue 30104: updated copyright

Tue, 02 Jun 2015 09:06:32 +0200Fixed issue 30104: Completed quantity in the Work Requirement is not updated
Jorge Garcia <jorge.garcia@openbravo.com> [Tue, 02 Jun 2015 09:06:32 +0200] rev 26989
Fixed issue 30104: Completed quantity in the Work Requirement is not updated

Completed quantity in the Work Requirement is not updated under some
circumstances.

The problem was that the ma_workeffort_validate wasn't updated the UPDATED
column of the ma_wrpahse table and you can save even if the line had changed in
the work effort window.

The solution is to update the column with the actual date. Now, when you try to
save it, a error appears in the grid and the save is canceled.

Thu, 04 Jun 2015 14:54:06 +0200Fixes issue 30063: Grid is properly loaded after refreshing with a selected row
Augusto Mauch <augusto.mauch@openbravo.com> [Thu, 04 Jun 2015 14:54:06 +0200] rev 26988
Fixes issue 30063: Grid is properly loaded after refreshing with a selected row

The problem was caused by this code (the this attribute is a ResultSet), which is contained in the fetchRemoteData function:

} else if (this.grid.refreshingWithSelectedRecord) {
// if the grid was refreshed with a record selected, use the range that contained that record
// instead of using targetRecordId to improve the performance
startRow = this.grid.selectedRecordInitInterval;
endRow = this.grid.selectedRecordEndInterval;
}

If the grid is refreshed while one of its records is selected, then the startRow and endRow will be set so that the requested page contains the selected record. The problem was that the ResultSet.localData attribute was not being properly set, as at this points it was expected to contain the 'loading' value for all the rows that are being requested. As a result of this the localData attribute became malformed when the response was processed, and this caused the grid to misbehave.

To fix this, the localData is configured to wait for the proper records:

this.localData = [];
this.setRangeLoading(startRow, endRow);

Thu, 28 May 2015 13:02:49 +0200Fixes issue 30019: Payment schedule amount incorrectly calculated.
Alvaro Ferraz <alvaro.ferraz@openbravo.com> [Thu, 28 May 2015 13:02:49 +0200] rev 26987
Fixes issue 30019: Payment schedule amount incorrectly calculated.

Payment schedule amount incorrectly calculated when adding a payment from reconcile window to a sales order.
FIN_TransactionProcess and PaidStatusEventHandler have been changed in order to set invoicepaid=true only when FIN_PaymentScheduleDetail has a related InvoicePaymentSchedule.
FIN_PaymentProcess.java has also been changed, in order to check invoicePaidAmounts only if FIN_PaymentScheduleDetail has a related InvoicePaymentSchedule.
In case of a payment to a order without an invoice, updatePaymentAmounts will be called only once.
Name of preference in UpdatePaymentPlan modulescript has been update to run it again and fix wrong data created by the issue.

Tue, 26 May 2015 18:20:34 +0200Fixed bug 30010: Error in Requisition To Order window
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Tue, 26 May 2015 18:20:34 +0200] rev 26986
Fixed bug 30010: Error in Requisition To Order window

When creating a purchase order from the Requisition To Order window, an error was raised when lines[i].quantityorder is empty.
Now the SQL query returns quantityorder = 0 when it's null. Then, when inserting the purchase order line, the process inserts "" if quantityorder = 0

Wed, 20 May 2015 14:06:47 +0200Fixes issue 29980: NPE in Add Payment process request
Alvaro Ferraz <alvaro.ferraz@openbravo.com> [Wed, 20 May 2015 14:06:47 +0200] rev 26985
Fixes issue 29980: NPE in Add Payment process request

When selecting a business partner with the magnifying glass in Add Payment process request, which does not match to the type of the document (a Vendor when the type is Received In); the payment method of the business partner was null and when accessing to its id, a NPE was raised.
Now, if payment method is null will be checked.