Fri, 12 Jun 2015 14:40:46 +0000CI: update AD_MODULE to version 26904
RM packaging bot <staff.rm@openbravo.com> [Fri, 12 Jun 2015 14:40:46 +0000] rev 26911
CI: update AD_MODULE to version 26904

Fri, 12 Jun 2015 12:49:18 +0200Related to issue 30082: code review improvements
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Fri, 12 Jun 2015 12:49:18 +0200] rev 26910
Related to issue 30082: code review improvements

The invoice's payment schedules and payment monitor is only updated when all the payment schedule details are paid.

This changeset covers the scenario where an order is partially paid. Before this change, the invoice's payment schedules and payment monitor were wrongly updated considering that the payment schedule was fully paid when any of its payment schedule details was paid. That asumption may be wrong in some scenarios, for example when the order is associated to one or more payment schedule details not yet paid (isinvoicepaid=N) and at least one already paid.

Wed, 10 Jun 2015 13:09:56 +0200Fixed issue 30082: Payment plan is updating wrong in some circumstances
Jorge Garcia <jorge.garcia@openbravo.com> [Wed, 10 Jun 2015 13:09:56 +0200] rev 26909
Fixed issue 30082: Payment plan is updating wrong in some circumstances

Payment plan is updating wrong if Payment Method is set as Automatic Receipt
and a sales order is partially paid.

The problem was that the function duplicates the value of the received amount
created in the Complete process of the invoice, because the function searches
all the payment details of the payment plan that has an invoice paid
(invoicepaid column).

The solution is to search those payment details that are not pre-paid and then
update the payment plan.

Now, the values are filled correctly.

Fri, 12 Jun 2015 12:05:42 +0200Related to issue 29972: code review improvements
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Fri, 12 Jun 2015 12:05:42 +0200] rev 26908
Related to issue 29972: code review improvements
Reduced useless query complexity to update outstanding amount.
It's only necessary to check fin_payment_detail_id is null (not associated payment) or isinvoicepaid='N' (associated payment but in a non paid yet status)

Wed, 10 Jun 2015 10:52:18 +0200Fixed issue 29972: Outstanding amount of sales order payment plan is not updated
Jorge Garcia <jorge.garcia@openbravo.com> [Wed, 10 Jun 2015 10:52:18 +0200] rev 26907
Fixed issue 29972: Outstanding amount of sales order payment plan is not updated

The problem was that the outstanding amount of sales order payment plan is not
updated when payment method is set as automatic receipt.

Before the commit which introduces this regression, the function checked the
status of the payment. With the changes, the function checks if the payment
schedule detail is paid.

The problem was in the update of the payment plan of the sales order,
specifically in WHERE clause for outstanding amount.

Now, the where clause works as expected, and the outstanding amount is updated
properly.

Fri, 12 Jun 2015 11:48:26 +0200Merged Heads
Martin Taal <martin.taal@openbravo.com> [Fri, 12 Jun 2015 11:48:26 +0200] rev 26906
Merged Heads

Thu, 11 Jun 2015 17:17:02 +0200Related to issue 29766: Retail Operations Buffer: store all transactions in operations table before processing
Martin Taal <martin.taal@openbravo.com> [Thu, 11 Jun 2015 17:17:02 +0200] rev 26905
Related to issue 29766: Retail Operations Buffer: store all transactions in operations table before processing
Initialize organisation structure provider before processing

Fri, 12 Jun 2015 10:32:21 +0200Fixes issue 30132: Product Transactions tab not showing records after filtering
Carlos Aristu <carlos.aristu@openbravo.com> [Fri, 12 Jun 2015 10:32:21 +0200] rev 26904
Fixes issue 30132: Product Transactions tab not showing records after filtering

The problem happened on the client filtering. In this case, the id of the property that references the parent tab is included in the criteria (using the convertCriteria function of the OBViewGrid class).
For those tabs which does not have any property (column) marked as link to parent, the parent property was not being requested to the datasource and when applying the criteria on the local filter the value for the parent property in every record was undefined. That was the reason why the filtering was not returning any record.
Now if the tab does not have any property set as link to parent, we look for the property pointing to the parent tab and include it in the selected properties returned by the datasource.

Thu, 11 Jun 2015 20:40:59 +0000CI: merge back from main
RM packaging bot <staff.rm@openbravo.com> [Thu, 11 Jun 2015 20:40:59 +0000] rev 26903
CI: merge back from main

Thu, 11 Jun 2015 20:23:04 +0000CI: update AD_MODULE to version 26898
RM packaging bot <staff.rm@openbravo.com> [Thu, 11 Jun 2015 20:23:04 +0000] rev 26902
CI: update AD_MODULE to version 26898