Tue, 16 Oct 2018 10:10:47 -0400Fixes issue 39454: "Create Lines From" on Goods Receipt not working properly
Mark <markmm82@gmail.com> [Tue, 16 Oct 2018 10:10:47 -0400] rev 35192
Fixes issue 39454: "Create Lines From" on Goods Receipt not working properly
when using Alternate UOM

Was taking as the AUM Qty the original value from the line instead of the value
defned on the P&E, this way if the value is changed, for instance for partiall receipts
then the process will create a line with the selected quantity instead of the entire
quantity of the original line wich is creating from.

Mon, 08 Oct 2018 14:46:08 +0200Fixes issue 39412: Prevents unintended formitem value change if focus changes
Augusto Mauch <augusto.mauch@openbravo.com> [Mon, 08 Oct 2018 14:46:08 +0200] rev 35191
Fixes issue 39412: 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 [^]

---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/form/ob-view-form.js: Enter commit message. Lines beginning with 'HG:' are removed.

Mon, 10 Dec 2018 16:29:15 +0100fixed issue 39672 use the new method getObjectLockForNoKeyUpdate
Sandra Huguet <sandra.huguet@openbravo.com> [Mon, 10 Dec 2018 16:29:15 +0100] rev 35190
fixed issue 39672 use the new method getObjectLockForNoKeyUpdate

Mon, 10 Dec 2018 16:26:15 +0100fixed issue 39755 change lockForNoKeyUpdate to return the instance with the lock
Sandra Huguet <sandra.huguet@openbravo.com> [Mon, 10 Dec 2018 16:26:15 +0100] rev 35189
fixed issue 39755 change lockForNoKeyUpdate to return the instance with the lock

*Retrieves an object from the database getting a lock "for no key update" for the indicated
object. Change method name, parameters and return.
*Improve and modify the javadoc with the required changes.

Wed, 05 Dec 2018 17:47:18 +0100Backed out changeset 26214ce6e789
Sandra Huguet <sandra.huguet@openbravo.com> [Wed, 05 Dec 2018 17:47:18 +0100] rev 35188
Backed out changeset 26214ce6e789

Wed, 05 Dec 2018 17:46:39 +0100Backed out changeset 58849d9510ba
Sandra Huguet <sandra.huguet@openbravo.com> [Wed, 05 Dec 2018 17:46:39 +0100] rev 35187
Backed out changeset 58849d9510ba

Wed, 05 Dec 2018 17:23:37 +0100related to issue 39672 lockForNoKeyUpdate not returns the id
Sandra Huguet <sandra.huguet@openbravo.com> [Wed, 05 Dec 2018 17:23:37 +0100] rev 35186
related to issue 39672 lockForNoKeyUpdate not returns the id

Wed, 05 Dec 2018 17:17:46 +0100related to issue 39755 code review changes
Sandra Huguet <sandra.huguet@openbravo.com> [Wed, 05 Dec 2018 17:17:46 +0100] rev 35185
related to issue 39755 code review changes

Not necessary to return the id. Only creates the lock.
Use createNativeQuery and improve code.

Tue, 04 Dec 2018 15:47:59 +0100related to issue 39672 use lockForNoKeyUpdate instead of lockFinAccount
Sandra Huguet <sandra.huguet@openbravo.com> [Tue, 04 Dec 2018 15:47:59 +0100] rev 35184
related to issue 39672 use lockForNoKeyUpdate instead of lockFinAccount

Use lockForNoKeyUpdate instead of use lockFinAccount in which a
"FOR UPDATE" is done and is too agressive.

Tue, 04 Dec 2018 15:42:37 +0100Fixed issue 39755 added in OBDAL lockForNoKeyUpdate
Sandra Huguet <sandra.huguet@openbravo.com> [Tue, 04 Dec 2018 15:42:37 +0100] rev 35183
Fixed issue 39755 added in OBDAL lockForNoKeyUpdate

new lockForNoKeyUpdate method to allow the use "FOR NO KEY UPDATE",
because "FOR UPDATE" in PostgreSQL is too aggressive.