Fixes Issue 31697:Bank Statement Line description overwritten with GL Item's
or payment's description when adding gl item or payment in add transaction
of Match Statement Process.

This issue is fixed in two area's
1. Add Transaction Process Definition window in Match Statement.
2. Transaction Tab of Financial Account window.

Whenever there exists a description prior adding gl item or payment in above
both cases description is appended with either gl item description or
payment description.

Fixed bug 31649: Performance problems opening Balance Sheet and PL structure

selectYearsDouble query was consuming most of the time required for launching the window.

Rewritten query to use EXISTS clause, to filter by AD_CLIENT_ID and to call AD_ORG_ISINNATURALTREE() function, which reduces the query cost from 126320.46 to 2527.97, and the time from 20 secs to 0,8 secs

Related to issue 31711: Add 2016 conversion rate and accounting for some assets

Fixes Issue 31711:Sample data (F&B International Group Client) for 3.0PR16Q1

Transactions created for Oct, Nov and Dec 2015 as per document "How to evolve
F&B"

Related To Issue 31711:Changes in sample data task while updating database
prior to creating transactions

Related to issue 29414: Updated browser supported/recommended list for PR16Q1

* Chrome. Supported 46, Recommended 47 or higher.
* Firefox. Supported 38, Recommended 38 or higher.
* Internet Explorer. Supported 9, Recommended 11 or higher.
* Safari. Supported 8, Recommended 9 or higher.

CI: merge back from main

CI: update AD_MODULE to version 28157

fixed bug 31758: error uploading attachments/images rendering OB in a frame

Whent trying to upload attachments/images in an application rendered in a frame,
JS errors were thrown.

This was caused because callback script for those actions assumed top was the
container for Openbravo, but when in a frame, top is the topmost frameset.

Fixed by checking if top is OB, and if not using parent instead.

CI: merge back from main

CI: update AD_MODULE to version 28154

fixed issue 31749: The warning message is not correct.

When a warning message had to be shown when saving a record, it was not the proper message.
It showed "Saving failed" text appended to the original warning message.
That was not correct because it was possible to save the record.
To fix this the "setMessage" function of the "ob-messagebar.js" has been changed.
Now, it appends the "Saving failed" message only if the message type is an error.

CI: merge back from main

CI: update AD_MODULE to version 28148

Fixes issue 31470: UniqueValidCombination modulescript is deactivating accounts

Add group by c_acctschema_id in selectDuplicates and updateValidCombinationDeactivateDuplicated queries in UniqueValidCombination modulescript.

Related to issue 31701: code review improvements

When reactivating an order, do not consider payments in Awaiting Payment status as payments really linked to the order. This is a way to ensure reactivation of orders already linked to a voided invoice is possible, because since #30971 a 0 amount payment is automatically when voiding an invoice.
So the flow in that case will be to manually reactivate that payment, and then reactivate the order.

Updated copyright year.

Fixes Issue 31701 It is not posible to modify order's payments ....
The C_ORDER_TRG2 trigger was updated to take into account sales invoices
with document status 'VO' when updating.

Fixes Issue 31473:Project Profitability report does not consider project
information set at invoice line

Invoice Line project information is used prior to Invoice project info.

Fixed bug 31695: Return to vendor shipments can be selected in return to vendor

The HQL query in charge of getting the shipment lines was wrongly including all the shipment documents. Instead it should be taking only the lines belonging to a non-return shipment document.

This feature was lost during the refactor to a manual datasource P&E

Merge back from main

Merge temporary head for 3.0PR15Q4.1

Added signature for changeset cf00bd72641c

Added tag 3.0PR15Q4.1 for changeset f698a5f953c8

Update AD_MODULE version to 3.0PR15Q4.1

fixes issue 31683: Some values are not shown in XLS format using MS Office

The detect cell type feature was not working properly for BigInteger values in Office after the Jasper Library Upgrade. A personalized format was applied causing the data not be shown when opening the report.

To solve this problem the detect cell type feature has been disabled. This way, by default, all the values in the XLS will be exported as strings.

This default configuration can be overriden at report level. As an example, the General Ledger Report and Trial Balance report have been updated properly. With this configuration, those reports are now using number formatting for the cells showing the BigDecimal values.

related to issue 31578: code review improvements

Fixes issue 31445: Import entry process can have a stopped but not deregistered thread: tickets remain in the queue
Adding log statements and catch block to prevent exiting loop

fixes issue 31578: alert fetches with where parameter

In order to avoid the fetching of the where parameter we generate the where clause inside the datasource. A new datasource has been created, ADAlertDatasourceService, to support the requests from the Alert Management window.

In addition, it has been fixed a problem in the Alert Rule drop-down filter of the grids in the Alert Management window which was displaying alert rules from all the grids in the window instead of those displayed just on a particular grid.

Fixes Issue 31628:Debit and Credit values not shown when running General
Ledger Report in XLS format using Microsoft Office 2007

Used Numberformat parameter to format the numeric fields

related to issue 31705: do not set singleDateMode after clearing filter values

The singleDateMode should not be set to true when clearing the filter values because this is preventing the date range dialog to appear under some circumnstances.