Thu, 05 Nov 2015 16:33:40 +0100fixes issue 31292: current combo value is not selected when opening drop down
Carlos Aristu <carlos.aristu@openbravo.com> [Thu, 05 Nov 2015 16:33:40 +0100] rev 27691
fixes issue 31292: current combo value is not selected when opening drop down

The problem is caused because after the combo refactor project table and tabledir references make use of a class with different behavior (OBFKComboItem).

Together with this, currently in the FormItem class there is a logic on the _shouldSelectOnFocus method which performs the selection just when tabbing through the form, or on programmatic focus, but not on mouse click. This is the main reason why the text is not being selected when clicking on the drop-down in form view for any reference.

In order to have a common behavior for all the combos in both grid and form view, we are overriding the showPicker() method of OBComboBoxItem to ensure that we select the text after clicking on the drop-down

Thu, 05 Nov 2015 11:59:31 +0100Fixed issue 31369: Added log to importentry processor
Guillermo Alvarez de Eulate <guillermo.alvarez@openbravo.com> [Thu, 05 Nov 2015 11:59:31 +0100] rev 27690
Fixed issue 31369: Added log to importentry processor

Tue, 03 Nov 2015 21:18:14 +0100Fixes issue 31348: Error when validating a Costing Rule with backdated enabled
Alvaro Ferraz <alvaro.ferraz@openbravo.com> [Tue, 03 Nov 2015 21:18:14 +0100] rev 27689
Fixes issue 31348: Error when validating a Costing Rule with backdated enabled

When checking for the current validated costing rule, it should have an ending date greater or equal than current date.

Tue, 27 Oct 2015 08:28:58 +0100fixed bug 31255: Lazy filtering does not work when filtering the first time
Asier Lostalé <asier.lostale@openbravo.com> [Tue, 27 Oct 2015 08:28:58 +0100] rev 27688
fixed bug 31255: Lazy filtering does not work when filtering the first time

Having lazy filtering configured, if a filter was applied in a grid as first
action, it was not possible to apply it. A js error was thrown:
Uncaught TypeError: this.data.willFetchData is not a function

The problem was in "if (this.data.willFetchData(this.convertCriteria(criteria)))"
statement which incorrectly assumed this.data to be an object and willFetchData
a function within it. This is not true when in this situation where this.data is
an array.

It has been fixed by taking into account this case by checking wether this.data
is an array.

Thu, 22 Oct 2015 18:29:49 +0200fixes issue 31224: Toolbar disappears under some circumnstances
Carlos Aristu <carlos.aristu@openbravo.com> [Thu, 22 Oct 2015 18:29:49 +0200] rev 27687
fixes issue 31224: Toolbar disappears under some circumnstances

Thu, 22 Oct 2015 15:26:37 +0200fixed bug 31218: adding extra filter after product characteristics fails
Asier Lostalé <asier.lostale@openbravo.com> [Thu, 22 Oct 2015 15:26:37 +0200] rev 27686
fixed bug 31218: adding extra filter after product characteristics fails

When product characteristics was filtered returning less than 100 records, and
on top of that criteria a new one in another field was added, it was not possible
to refresh the grid anymore.

When this additional criteria was set, a javascript exception was thrown because
adaptive filtering was tried to be evaluated for 'exists' search operator. This
operator didn't implement condition funtion which was invoked causing the exception.
This exception left the grid in an inconsistent estate which made not posible to
refresh it.

To fix it, 'condition' function has been implemented for 'exists' search operator,
as this operator can't be evaluted in client side, we can ensure all fields in
grid fulfill any criteria defined by it, so the implementation can return always
true.

Mon, 19 Oct 2015 12:38:32 +0200Fixed bug 31167: Copy Version process in Process Plan window is not working in Oracle
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Mon, 19 Oct 2015 12:38:32 +0200] rev 27685
Fixed bug 31167: Copy Version process in Process Plan window is not working in Oracle

Ad_Sequence_Doc is a stored procedure that returns the next sequence number using an "out" parameter. The CallStoredProcedure.call() used to call that procedure doesn't currently support parameters of type "out", creating an exception in Oracle only (and not in PostgreSQL because the procedure is declared as a function returning the value).

Instead of calling the procedure using CallStoredProcedure.call(), we use Utility.getDocumentNo() method instead, which is a more standard way to get the next sequence no. from Java, and supports Oracle procedures with "out" parameters.

Besides the class has been modified to properly show an error message in the UI in case an exception is raised, which is something not working before neither.

Thu, 15 Oct 2015 10:34:40 +0200Related with issue 31054: The condition has been changed.
Naroa Iriarte <naroa.iriarte@openbravo.com> [Thu, 15 Oct 2015 10:34:40 +0200] rev 27684
Related with issue 31054: The condition has been changed.

The if condition which handles the invalidation of the value maps cache has been modified for getting the correct behaviour.

Wed, 14 Oct 2015 15:37:35 +0200Fixed issue 31054: Create a new record in a form was not working fine.
Naroa Iriarte <naroa.iriarte@openbravo.com> [Wed, 14 Oct 2015 15:37:35 +0200] rev 27683
Fixed issue 31054: Create a new record in a form was not working fine.

The problem was that, if you create a new record in form view, and after fulfilling the form, you
click in the create a new record in a form button without previously saving the firstly created record,
it was not working fine. In Goods Movements lines tab, for example, the value of the product chosen in
the first record was shown. That wasn't correct, the product should be empty.

The problem was in the "ob-standard-view-datasource.js" the value map cache was being invalidated.

To fix this, some clases have been changed.
In the "ob-standard-view.js" in the "newDocument" function the parameters the isNewDocument parameter
has been added and it is set to true.
This parameter is passed to the request for being able to take it in the class "ob-standard-view-datasource.js"
and to use it in the logic that invalidates the value map cache.

Wed, 30 Sep 2015 16:13:10 +0200Fixed bug 31088: Scheduled Organization for Costing background process
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Wed, 30 Sep 2015 16:13:10 +0200] rev 27682
Fixed bug 31088: Scheduled Organization for Costing background process

The Costing Background Process should only be scheduled for a legal entity or any of its ancestor.

The fix adds a validation in both the ProcessRequestEventHandler, so each time a record is saved/updated the validation is run, and in the CostingBackground class itself to control wrong process request scheduled before this validation.

Fri, 02 Oct 2015 12:39:49 +0200Fixed bug 31021: hidden fields in several windows related to acct. dimensions
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Fri, 02 Oct 2015 12:39:49 +0200] rev 27681
Fixed bug 31021: hidden fields in several windows related to acct. dimensions

The display logic of some fields driven by the accounting dimension display logic utility was not working fine when the auxiliary input "DOCBASETYPE" (used by to calculate the acct. dimension display logic) was null.
This auxiliary input has a hardcoded value in some windows, however in other windows it is gotten from the DB using the selected document type. In the latter scenario, when the document type field is blank, the "DOCBASETYPE" auxiliary input was null, so the system was unable to detect the right configuration, thus hiding the fields.

The regression is caused by issue #29767. The business partner and organization fields were configured to use the accounting dimension display logic utility in the following windows:
* Sales Order
* Purchase Order
* Sales Invoice
* Purchase Invoice
* Payment In (not affected as it has a hardcoded "DOCBASETYPE")
* Payment Out (not affected as it has a hardcoded "DOCBASETYPE")

The fix improves the SQL for getting the "DOCBASETYPE" auxiliary input in the affected windows, so in case the document type is null, a generic value (the most commonly used) is returned depending on the window:
* Sales Order: SOO
* Purchase Order: POO
* Sales Invoice: ARI
* Purchase Invoice: API

Fri, 02 Oct 2015 12:24:48 +0200Fixes issue 31031: Credit consumed although payment not completed
Alvaro Ferraz <alvaro.ferraz@openbravo.com> [Fri, 02 Oct 2015 12:24:48 +0200] rev 27680
Fixes issue 31031: Credit consumed although payment not completed

When consuming a credit with a currency different than Business Partner's currency, an error is shown but credit was also consumed, which was wrong.
Now, this check will be also done before consuming credit in AddPaymentActionHandler addCredit method, as it was done in FIN_PaymentProcess doProcessPayment method.

Tue, 03 Nov 2015 13:09:00 +0000Merge temporary head for 3.0PR15Q3.3
RM packaging bot <staff.rm@openbravo.com> [Tue, 03 Nov 2015 13:09:00 +0000] rev 27679
Merge temporary head for 3.0PR15Q3.3

Tue, 03 Nov 2015 05:40:14 +0000Added signature for changeset d20a396ffa24
RM packaging bot <staff.rm@openbravo.com> [Tue, 03 Nov 2015 05:40:14 +0000] rev 27678
Added signature for changeset d20a396ffa24

Tue, 03 Nov 2015 05:40:14 +0000Added tag 3.0PR15Q3.3 for changeset bce57079bd43
RM packaging bot <staff.rm@openbravo.com> [Tue, 03 Nov 2015 05:40:14 +0000] rev 27677
Added tag 3.0PR15Q3.3 for changeset bce57079bd43