Thu, 02 Feb 2017 17:40:19 +0100Related to issue 35089 and related to issue 35130:
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Thu, 02 Feb 2017 17:40:19 +0100] rev 31547
Related to issue 35089 and related to issue 35130:

Added missed subclasses .class files

Thu, 02 Feb 2017 17:21:08 +0100Related to issue 35089 and related to issue 35130:
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Thu, 02 Feb 2017 17:21:08 +0100] rev 31546
Related to issue 35089 and related to issue 35130:

Declare merge for modules:
* Aging Balance Report
* Cashflow Forecast Report

Added buildvalidation to check:
1. Both merged modules are not inside modules folder
2. There are no modules in the instance that depend on any of the merged modules

Thu, 02 Feb 2017 09:50:40 +0100Related to issue 35089: code review improvements
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Thu, 02 Feb 2017 09:50:40 +0100] rev 31545
Related to issue 35089: code review improvements
Fixed amounts format in XLS views

Wed, 01 Feb 2017 18:01:07 +0100Related to issue 35130: code review improvements
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Wed, 01 Feb 2017 18:01:07 +0100] rev 31544
Related to issue 35130: code review improvements

Fixed db consistency.
Reused core's messages instead of creating new ones.
Deleted 2 jrxml files that are not needed.
Properly set menu entry for new report.
Fixed issue that hid the first record in HTML/PDF view (not XLS).
Usage of AMOUNTFORMAT and patternExpression based on it.
Removed useless SQL queries in JRXML files.
Make Strings in reports translatable.
Several jasper UI improvements: padding, link behavior, borders...

Wed, 21 Dec 2016 14:06:05 -0500Fixed issue 35130: Merged Cashflow Forecast Report into Core
Rafael Queralta Pozo <rqueralta@nauta.cu> [Wed, 21 Dec 2016 14:06:05 -0500] rev 31543
Fixed issue 35130: Merged Cashflow Forecast Report into Core

Tue, 31 Jan 2017 10:17:23 +0100Related to issue 35089: code review improvements
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Tue, 31 Jan 2017 10:17:23 +0100] rev 31542
Related to issue 35089: code review improvements

Simplified exception management.
Fixed execution of PDF and XLS in details view.
Transform index to partial index for not null values.
Fixed DB consistency.
Renamed Day One/Two/... by Group One/Two/...
Use AMOUNTFORMAT instead of NUMBERFORMAT.
Removed useless parameters.
Retrieved @basedesign@ from ReportingUtils.

Thu, 08 Dec 2016 11:33:43 -0500Fixed issue 35089: Merged Aging Balance Report into Core
Nono Carballo <nonofce@gmail.com> [Thu, 08 Dec 2016 11:33:43 -0500] rev 31541
Fixed issue 35089: Merged Aging Balance Report into Core

The following actions has been made

- Dependencies to 2.5 were removed.
- Reports in PDF and XLS format were taken from the module and left unchanged.
- Reports in HTML format were modified to allow navigation between reports
and export to PDF and XLS format.
- Functions AGING_GETDOCNO, AGING_INVOICECURRENCY_RATE, AGING_ISDOUBTFULTDEBT and
AGING_PAYMENTCURRENCY_RATE were renamed to FIN_AGING_GETDOCNO,
FIN_AGING_INVOICECURRENCY_RATE, FIN_AGING_ISDOUBTFULTDEBT and
FIN_AGING_PAYMENTCURRENCY_RATE, and updated the file AgingDao_data.xsql,
where were calles.
- An index on column FIN_PAYMENT_SCHEDULE_ID was added to table FIN_DOUBTFUL_DEBT
- Two new Process Definitions were added, one for Payables Aging Schedule Report
and other for Receivables Aging Schedule Report; defined parameters, default
values and validation rules for each one.
- Two new menu entries were created to invoke the Process Definition.
- A new action handler was created (AgingBalanceReportActionHandler), extending
BaseReportActionHandler, holding the logic to process both reports.

Tue, 21 Feb 2017 16:04:04 -0500Fixes issue 34993: Update the invoice prepayment amount with correct value
Mark <markmm82@gmail.com> [Tue, 21 Feb 2017 16:04:04 -0500] rev 31540
Fixes issue 34993: Update the invoice prepayment amount with correct value
if after create from a paid order line, it updates the line net amount to 0
or it changes from 0 to a another value.

If you create the invoice line from a paid order line, and then the line net amount
changes it value to 0 (by updating qty = 0 or price = 0, for instance), then
previously prepayment was remaining instead of be discarded. So, you may have an
invoice with Total Gross Amount of 0 and a prepayment different than 0.

When you are updating a line with a NEW line net amount = 0 or deleting the line,
it is needed to remove the prepayment of this line from the invoice.

If the OLD line net amount was zero (the prepayment was removed or not taken into
account when creating or updating the line) and it changes
to a non-zero new line net amount value, is necessary take into account the prepaid
order line amount to increase the invoice prepayment amount with its value.

In any other case it is not necessary update the prepayment amount of the invoice.

Wed, 22 Feb 2017 14:14:23 +0100related with bug 20515: OBCriteria creates contention at JVM
Asier Lostalé <asier.lostale@openbravo.com> [Wed, 22 Feb 2017 14:14:23 +0100] rev 31539
related with bug 20515: OBCriteria creates contention at JVM

Same fix for missing createCriteria with alias.

Mon, 20 Feb 2017 10:26:49 -0500Fix for issue 35129: Calculate Standard Costs check records from other clients
Armaignac <collazoandy4@gmail.com> [Mon, 20 Feb 2017 10:26:49 -0500] rev 31538
Fix for issue 35129: Calculate Standard Costs check records from other clients

The Calculate Standar Costs Process was checking records from other clients for
a missing client check in the process

The client check was add in the process in order to get the current client records