Thu, 11 Oct 2018 09:26:50 +0200fixed issue 39141: removed ant tomcat.reload task
Asier Lostalé <asier.lostale@openbravo.com> [Thu, 11 Oct 2018 09:26:50 +0200] rev 34838
fixed issue 39141: removed ant tomcat.reload task

This task is unused for years now.

Thu, 11 Oct 2018 08:57:47 +0200Fixes issue 39355: Issue a partial sales order line if there is a reservation
Nono Carballo <nonofce@gmail.com> [Thu, 11 Oct 2018 08:57:47 +0200] rev 34837
Fixes issue 39355: Issue a partial sales order line if there is a reservation

* Checks the reservation exists before reallocate it if it does not have enough
stock reserved.

Fri, 05 Oct 2018 11:41:53 +0200Fixes issue 39373: Prevents unintended formitem value change if focus changes
Augusto Mauch <augusto.mauch@openbravo.com> [Fri, 05 Oct 2018 11:41:53 +0200] rev 34836
Fixes issue 39373: Prevents unintended formitem value change if focus changes

There was a problem in this redraw function [1]. It did the following:
1) Get the value of the focused item (this.getFocusItem().getValue())
2) Redraw the form (this.Super('redraw', arguments);)
3) Restore the value of the focused item if the value changed during the redraw (this.getFocusItem().setElementValue(focusItemValue);)

The problem was that under some circumstances the focusedItem itself changed during the redraw, so the form items returned by this.getFocusItem()
in steps 1) and 3) are different, and the value from one form item was copied into another form item.

This problem has been fixed by storing in a variable the focused form item before the step 1), and the use that reference in the rest of the
function instead of reinvoking this.getFocusItem()

[1] https://code.openbravo.com/erp/devel/pi/file/tip/modules/org.openbravo.client.application/web/org.openbravo.client.application/js/form/ob-view-form.js#l2157

Wed, 03 Oct 2018 12:58:44 -0400Fixes issue 39367:Set some columns to be stretched with overflow to avoid be cut
Mark <markmm82@gmail.com> [Wed, 03 Oct 2018 12:58:44 -0400] rev 34835
Fixes issue 39367:Set some columns to be stretched with overflow to avoid be cut

Some columns where cells can show long text are set as stretch with overflow and
with stretch type = "RelativeToTallestObject" to align and stretch correctly

Tue, 02 Oct 2018 16:49:40 +0200Fixed bug 39391: Movements in same bin for non-attribute product
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Tue, 02 Oct 2018 16:49:40 +0200] rev 34834
Fixed bug 39391: Movements in same bin for non-attribute product

The goods movement created by AWO when a product has no attribute are automatically set with m_attributesetinstance_id = '0'.
In a normal movement the m_attributesetinstanceTO_id is usually null (unless an attribute change or a RI related flow involved). Thus the comparation has '0'='X' which avoided to raise the expected error.

Note that in Core the m_attributesetinstance_id for non-attribute product is NULL, so the issue is not reproducible in Core. Besides the UI controls this scenario very well.

The solution is done in the trigger rather than in AWO because it is safer and easier to develop.
It runs the locators check only when m_attributesetinstanceTO_id is null.
If m_attributesetinstanceTO_id is not null it implies an attribute change or a RI related movement, and in any of these cases it is allowed to run the movement within the same bin.

Tue, 02 Oct 2018 09:43:11 +0200related to issue 39362: added test cases covering no DB conns detection
Asier Lostalé <asier.lostale@openbravo.com> [Tue, 02 Oct 2018 09:43:11 +0200] rev 34833
related to issue 39362: added test cases covering no DB conns detection

Fri, 28 Sep 2018 08:03:08 +0200fixed issue 39362: can't create tickets if one failed due to pool without conns
Asier Lostalé <asier.lostale@openbravo.com> [Fri, 28 Sep 2018 08:03:08 +0200] rev 34832
fixed issue 39362: can't create tickets if one failed due to pool without conns

After a ticket failed to be imported due to the pool is out of connections, no
new tickets can be created from that terminal until all import entries are set
again in Initial status.

Now in this case instead of setting the import entry as Error preventing new
tickets from the same terminal to be processed, it's kept in Initial status,
in this way it will be tried to be processed in next cycle, not exposing the
problem to users.

Wed, 03 Oct 2018 17:18:12 +0200related to issue 39318 set a properly name to variable and function
Sandra Huguet <sandra.huguet@openbravo.com> [Wed, 03 Oct 2018 17:18:12 +0200] rev 34831
related to issue 39318 set a properly name to variable and function

Wed, 03 Oct 2018 10:21:31 +0200Fixes issue 39335: Wrong combination of General Ledger and accounts
Nono Carballo <nonofce@gmail.com> [Wed, 03 Oct 2018 10:21:31 +0200] rev 34830
Fixes issue 39335: Wrong combination of General Ledger and accounts

* A new Event Observer was created to check, on save, if Debit and Credit
accounts belongs to the selected Accounting Schema.

Tue, 02 Oct 2018 17:45:00 +0200Fixed issue 39318 Wrong accounting entry for a doubtful debt payment
Sandra Huguet <sandra.huguet@openbravo.com> [Tue, 02 Oct 2018 17:45:00 +0200] rev 34829
Fixed issue 39318 Wrong accounting entry for a doubtful debt payment
if the invoice has more than one payment plan detail

When more that one payment schedule detail, set the doubtful debt amount correctly.