Tue, 25 Apr 2017 18:26:55 +0200Related to issue 35772: Fix dbcons failure
Alvaro Ferraz <alvaro.ferraz@openbravo.com> [Tue, 25 Apr 2017 18:26:55 +0200] rev 31983
Related to issue 35772: Fix dbcons failure

Tue, 25 Apr 2017 17:34:18 +0200Fixed issue 35782: compile.complete.deploy depend on core.lib,wad.lib,trl.lib
Inigo Sanchez <inigo.sanchez@openbravo.com> [Tue, 25 Apr 2017 17:34:18 +0200] rev 31982
Fixed issue 35782: compile.complete.deploy depend on core.lib,wad.lib,trl.lib

Compile.complete.deploy ant task now is depent on core.lib,wad.lib,trl.lib because if deploy.mode
in Openbravo.properties is configured to class mode compile.complete.development ant task is
executed and now this task depend on core.lib,wad.lib and trl.lib.

On the other hand if deploy.mode in Openbravo.properties is configured to war mode, compile.complete
is executed and this ant task has the dependencies defined properly.

Wed, 12 Apr 2017 12:53:42 -0400Fixes issue 35772: Orders with Invoice Terms different from Customer Schedule
Mark <markmm82@gmail.com> [Wed, 12 Apr 2017 12:53:42 -0400] rev 31981
Fixes issue 35772: Orders with Invoice Terms different from Customer Schedule
After Delivery cannot be invoiced if the bp has an invoice schedule

Sales Orders with Invoice Terms different from Customer Schedule After Delivery
(Immediate, After Delivery, After Order Delivered) cannot be invoiced if the business
partner has an invoice schedule defined and the order does not fill its requirement

The problem is that the order is not returned by the C_INVOICE_CANDIDATE_V view.
To avoid it was fixed the condition that takes into account the invoice rule of
the order and the sales invoice frequency.

Tue, 25 Apr 2017 15:59:15 +0200fixed bug 35834: platform modules fail in CI
Asier Lostalé <asier.lostale@openbravo.com> [Tue, 25 Apr 2017 15:59:15 +0200] rev 31980
fixed bug 35834: platform modules fail in CI

Two different instances of Weld bean manager were in use, this caused dependant
context not to be consistently handled in jUnit Arquillian test cases.

Solved by setting the same instance for static and instance bean manager in WeldUtils
whenever a test class is statarted.

Sun, 16 Apr 2017 13:16:12 -0400Fixes issue 35636: Business partner selector get stuck in create lines from
Mark <markmm82@gmail.com> [Sun, 16 Apr 2017 13:16:12 -0400] rev 31979
Fixes issue 35636: Business partner selector get stuck in create lines from
invoice in hgvol environment

In high volume environment, when the Business Partner selector is opened from Create
lines from process in the Invoice window, it takes too long to load results and as
consequence the browser was stocked.

To improve the performance in this selector, was changed the BusinessPartner_data.xsql
methods to use UPPER instead of C_IGNORE_ACCENT function, this way it uses the index
created in issue 35210 and improves of performance it introduces.

Mon, 24 Apr 2017 18:41:02 +0200fixes bug 35825: Default org/warehouse not sorted properly in profile widget
Carlos Aristu <carlos.aristu@openbravo.com> [Mon, 24 Apr 2017 18:41:02 +0200] rev 31978
fixes bug 35825: Default org/warehouse not sorted properly in profile widget

After the changes introduced on issue #35553, the content of the profile widget fields (role, organization, warehouse) is sorted in the client side. The sorting was already being done when displaying the pick lists, but the value map used by those fields was not being sorted.

The default value of the org/warehouse fields when changing the role is the first value of their respective value maps. For this reason, since now the value maps for those fields is always sorted: the OB.User.userInfo object is instantiated with the mentioned value maps sorted by identifier, thanks to the call to 'sortByProperty' added in the user-info.js.ftl template.

Mon, 24 Apr 2017 12:06:00 +0200Related with issue 35658: Codereview take into account all the cases
Inigo Sanchez <inigo.sanchez@openbravo.com> [Mon, 24 Apr 2017 12:06:00 +0200] rev 31977
Related with issue 35658: Codereview take into account all the cases

Now it is take into account when a parameter window with grid is opened from the menu.
Rest of the cases sucha as grid, form and parameter window from a button is working as
expected too.

Mon, 24 Apr 2017 10:25:52 +0200fixes bug 29006: provide info of the pressed button in client side validations
Carlos Aristu <carlos.aristu@openbravo.com> [Mon, 24 Apr 2017 10:25:52 +0200] rev 31976
fixes bug 29006: provide info of the pressed button in client side validations

Fri, 21 Apr 2017 14:28:27 +0200fixes issue 35769: Firefox browser freezed sometimes after showing some pop-ups
Carlos Aristu <carlos.aristu@openbravo.com> [Fri, 21 Apr 2017 14:28:27 +0200] rev 31975
fixes issue 35769: Firefox browser freezed sometimes after showing some pop-ups

After the changes introduced in project [1], there was a race condition reproducible in Firefox (not in Chrome).

The heartbeat/registration pop-ups are now displayed before the moment they were shown. Together with this, when generating the content of the pop-up, the standard document.write() is used since the very beginning, and according to the documentation[2] it is recommended to call document.close() to tell the browser to finish loading the page.

The document.close() was not being used and this seems to be the root cause of the race condition: by adding this function Firefox is not getting blocked and the instabilities in CI are gone.

[1] http://wiki.openbravo.com/wiki/Projects:Login_Process_Perfomance_Improvements
[2] https://developer.mozilla.org/en-US/docs/Web/API/Document/write

Fri, 21 Apr 2017 13:55:46 +0200Fixed issue 35658: Fields redraw instantly in grid under some circumstances
Inigo Sanchez <inigo.sanchez@openbravo.com> [Fri, 21 Apr 2017 13:55:46 +0200] rev 31974
Fixed issue 35658: Fields redraw instantly in grid under some circumstances

The problem was that numeric fields redraws instantly in grid view when a numeric field
was referenced by a read only logic. This reported problem was caused by the partial fix
of #32202 regression.

The fix of #32202 was partial because the added condition did not taken into account the
grid view properly. This problem has been resolved by take into account form and grid view.

Besides another problem was found and resolved with this fix. Since this regression was
introduced, the #23136 issue was broken too. This problem has been resolved too with this
solution.