Mon, 27 Apr 2015 13:51:37 +0200Fixes Issue 29680:Add details pop up in Payment Out window filters records
Eduardo Argal Guibert <eduardo.argal@openbravo.com> [Mon, 27 Apr 2015 13:51:37 +0200] rev 26495
Fixes Issue 29680:Add details pop up in Payment Out window filters records
with supplier reference

having clause fixed to take into account supplier reference

Mon, 27 Apr 2015 16:52:31 +0200Fixed issue 29697: Description field is set with "null" in the FA Transaction
Jorge Garcia <jorge.garcia@openbravo.com> [Mon, 27 Apr 2015 16:52:31 +0200] rev 26494
Fixed issue 29697: Description field is set with "null" in the FA Transaction

Description field is filled in with "null" in the FA Transaction when matched
to GL Item.

The problem was in the Match Statement process, more specifically, in the
Add new transaction button. The AddTransanctionActionHandler didn't
take in consideration that the received description could be null.

The fix for this issue is to check if the received description is null
or blank.

Now, the description field fill in the correct description.

Mon, 30 Mar 2015 21:27:03 -0500Fixed bug 28702: Assets Organization should not be changed if it has lines
Reinaldo Guerra <reinaldo.guerra@peoplewalking.com> [Mon, 30 Mar 2015 21:27:03 -0500] rev 26493
Fixed bug 28702: Assets Organization should not be changed if it has lines

Like happens in other windows such as Products and Business Partner, the organization's field behaviour in Assets window was changed to not be updatable.
Now when the Assets record is saved, it is not possible to change its organization, so there will not be inconsistencies with previous created lines if the amortizations are recalculated.

Mon, 27 Apr 2015 18:58:05 +0200Fixed bug 28927: Filter is removed when cancel transactions from Match process
Unai Martirena <unai.martirena@openbravo.com> [Mon, 27 Apr 2015 18:58:05 +0200] rev 26492
Fixed bug 28927: Filter is removed when cancel transactions from Match process

Changed OB.APRM.MatchStatement.onRefresh function in a similar way to OB.APRM.AddPayment.currencyOnChange function.
The previous criteria is kept (including the selected record) and used again to refresh the grid records and redraw the form.

Thu, 16 Apr 2015 18:33:31 +0200Fixes issue 29616: Error in GLJournalAccountingCheck validation
Alvaro Ferraz <alvaro.ferraz@openbravo.com> [Thu, 16 Apr 2015 18:33:31 +0200] rev 26491
Fixes issue 29616: Error in GLJournalAccountingCheck validation

Query in GLJournalAccountingCheck build validation has been changed to avoid build validation fail, when exists a negative gl journal line and system is configured to "not allow negative amount" during posting, although accounting information is correct

Mon, 27 Apr 2015 19:22:06 +0200Fixes issue 27951
Eduardo Argal Guibert <eduardo.argal@openbravo.com> [Mon, 27 Apr 2015 19:22:06 +0200] rev 26490
Fixes issue 27951
Record is automatically deleted from "General Ledgers" tab when "Organization" record is updated
Now eventhandler just attends changes in general ledger info

Mon, 27 Apr 2015 18:20:37 +0200Related to issue 29119: Search for conversion rate when different currencies
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Mon, 27 Apr 2015 18:20:37 +0200] rev 26489
Related to issue 29119: Search for conversion rate when different currencies

The code in charge of getting the conversion rate will be executed only for different currencies

Mon, 27 Apr 2015 18:11:20 +0200Related to issue 29119: Applied OB code format
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Mon, 27 Apr 2015 18:11:20 +0200] rev 26488
Related to issue 29119: Applied OB code format

Wed, 11 Mar 2015 10:44:04 -0500Fixed bug 29119: "Use credit" process should consider defined conversion rate.
Reinaldo Guerra <reinaldo.guerra@peoplewalking.com> [Wed, 11 Mar 2015 10:44:04 -0500] rev 26487
Fixed bug 29119: "Use credit" process should consider defined conversion rate.

The currencies conversion rate, defined for payment's date, is now taken into account when the credit left by the payment, is used during the invoice's process.
Now the field exange rate, is well defined in the new payment created, if exists a conversion between the currencies of the invoice's and the payment's financial account, for the payment's date.

Mon, 27 Apr 2015 17:58:00 +0200Fixed bug 28503: Not BOM included in another BOM, is not automatically exploded.
Unai Martirena <unai.martirena@openbravo.com> [Mon, 27 Apr 2015 17:58:00 +0200] rev 26486
Fixed bug 28503: Not BOM included in another BOM, is not automatically exploded.

Stored procedure called M_EXPLODEBOMNOTSTOCK, was changed to make a recursive call to itself, while a new order line is created with BOM and not stocked products.
Now a not stocked BOM product included in another not stocked BOM product, is automatically exploded, when booking order lines.
This change also affects the explode direct process called from Explode button in order lines tab.