Thu, 13 Aug 2015 04:34:37 +0000Update AD_MODULE version to 3.0PR15Q3 3.0PR15Q3
RM packaging bot <staff.rm@openbravo.com> [Thu, 13 Aug 2015 04:34:37 +0000] rev 27573
Update AD_MODULE version to 3.0PR15Q3

Tue, 11 Aug 2015 09:23:51 +0200Related to issue 30531: updated revision control number
Carlos Aristu <carlos.aristu@openbravo.com> [Tue, 11 Aug 2015 09:23:51 +0200] rev 27572
Related to issue 30531: updated revision control number

Mon, 10 Aug 2015 14:26:44 +0200Fixes issue 30531: Openbravo ERP 3 doesn't work on Microsoft Edge
Carlos Aristu <carlos.aristu@openbravo.com> [Mon, 10 Aug 2015 14:26:44 +0200] rev 27571
Fixes issue 30531: Openbravo ERP 3 doesn't work on Microsoft Edge

The application was crashing silently during the login process, because Smartclient sources were not identyfing properly the browser. This caused an error in the SC getStackTrace() method. In addition, the OB function getBrowserInfo() has been updated to identify the Microsft Edge browser in order to declare it as not supported for the time being

Mon, 10 Aug 2015 10:23:33 +0530Fixes Issue 30528:Potential full c_orderline scan in M_Reservation_trg
Atul Gaware <atul.gaware@openbravo.com> [Mon, 10 Aug 2015 10:23:33 +0530] rev 27570
Fixes Issue 30528:Potential full c_orderline scan in M_Reservation_trg

Removed unwanted line in code which fully scans c_orderline.

Mon, 03 Aug 2015 23:08:59 +0530Fixes Issue 30490: Return from Customer Pick&Edit Lines allows to enter more
Atul Gaware <atul.gaware@openbravo.com> [Mon, 03 Aug 2015 23:08:59 +0530] rev 27569
Fixes Issue 30490: Return from Customer Pick&Edit Lines allows to enter more
quantity to return than the pending to be returned

Return document has negative movementqty so ReturnQtyOtherRM was negative.
It should be postive so unlike ReturnQty it is multiplied with -1 as in prev
Datasource prior to transforming it to HQL PE. Where clause which checks
MovementQty of shipment line with the ReturnQtyOtherRM was missing. Sum of
Shipmentline MovementQty and ReturnQtyOtherRM should not be zero. It is added
to fix the problem.

Thu, 23 Jul 2015 17:27:54 +0200Fixes issue 30420. Fixes problem in a Query condition.
David Miguelez <david.miguelez@openbravo.com> [Thu, 23 Jul 2015 17:27:54 +0200] rev 27568
Fixes issue 30420. Fixes problem in a Query condition.
The = comparasion must be changed with >

Thu, 23 Jul 2015 17:16:08 +0200Fixes issue 30417. Initialize global variable each time to
David Miguelez <david.miguelez@openbravo.com> [Thu, 23 Jul 2015 17:16:08 +0200] rev 27567
Fixes issue 30417. Initialize global variable each time to
make sure it does not uses values from a previous execution.

Thu, 23 Jul 2015 17:05:01 +0200Fixes Issue 30414. Refreshes Transaction Object before accessing to it
David Miguelez <david.miguelez@openbravo.com> [Thu, 23 Jul 2015 17:05:01 +0200] rev 27566
Fixes Issue 30414. Refreshes Transaction Object before accessing to it
again to fix a LazyInitializationException Hibernate exception.
Also removes unnecessary save, since flush is done afterwards.

Thu, 23 Jul 2015 13:51:40 +0200Fixes issue 30404: selectors not working in grid view when display field is set
Carlos Aristu <carlos.aristu@openbravo.com> [Thu, 23 Jul 2015 13:51:40 +0200] rev 27565
Fixes issue 30404: selectors not working in grid view when display field is set

When setting the display field for a selector with FKSelectorUIDefinition as its UI Definition class, if the display field was referencing to a property of the main entity of the selector, the display field name returned as part of the gridProps in the view definition was 'entity'.
The _extraProperties in the datasource used by the selector does not contain the entity name if they are referencing to the main entity. That is the root of the problem: when trying to set the selected value of the selector picklist in grid view, the display field name was never found as we were using 'entity' instead of looking directly for 'property'.
This problem does not affect when setting as display field a field that references a property which does not belong to the main entity of the selector.
To solve this problem, now in FKSelectorUIDefinition we return 'property' as the display field name instead of 'entity' when the property belongs to the main entity.

Fri, 17 Jul 2015 15:04:27 +0200Related to Issue 30332: Do not take into account Transactions in Skip Status.
David Miguelez <david.miguelez@openbravo.com> [Fri, 17 Jul 2015 15:04:27 +0200] rev 27564
Related to Issue 30332: Do not take into account Transactions in Skip Status.
Remove them from the queries.
In Costing Server, set all Transactions as isProcessed=Y when they go through
doProcess() method.