int-basic-oracle - Build # 878 - Fixed:
Check console output at https://ci.openbravo.com/job/int-basic-oracle/878/ to
view the results.
Committers since last success:
Changes for Build #876
Rafa Alonso <[email protected]> null
Related issue 28190: Failing to drop the database will cause the build to
fail (II)
After Stefan feedback:
- the fix now makes use of the existing DROP in the "clean.database.POSTGRE"
task. The change is that the build will but the build fail if the drop fails.
- the "clean.database.POSTGRE" task is being accessed by the <target
name="create.database"> task.
Note that the "clean.database.ORACLE" task has not been in this changeset.
src-db/database/build-create.xml
Unai Martirena <[email protected]> null
Fixes bug 29615: Correctly used credit when paying an invoice and refunding
There were two issues while managing this scenario:
[1] In 'addCredit' method inside AddPaymentActionHandler.java class, a loop of
Credit to Use grid is done, creating Payment Credit Used records assigned to
the new created payment of the invoice. This method was not taking into account
that could be credit amount that exceeds the invoice amount (amount to be
refunded) and it was assigning all the credit amount as used to the payment of
the invoice. So the refund payment that is created right after was been left
without any used credit payment.
[2] After fixing the previous method, the second issue appears. The
'updateUsedCredit' method inside FIN_PaymentProcess.java class retrieves all
the payments of the business partner that has generated credit, and it assigns
as used to the refund payment. The problem with this function is that before
the Add Payment refactor it was not possible to select which credit payments we
wanted to consume, it was only a total credit amount to be consumed and the
system behind was being consuming any of them. But after the refactor it is
possible to select the ones that want to be consumed.
In order to fix this last issue the selected credit line ids are added as a
parameter to 'updateUsedCredit' method.
modules/org.openbravo.advpaymentmngt/src/org/openbravo/advpaymentmngt/actionHandler/AddPaymentActionHandler.java
modules/org.openbravo.advpaymentmngt/src/org/openbravo/advpaymentmngt/process/FIN_AddPayment.java
modules/org.openbravo.advpaymentmngt/src/org/openbravo/advpaymentmngt/process/FIN_PaymentProcess.java
Changes for Build #877
Atul Gaware <[email protected]> null
Fixes Issue 29509:Process Price Difference Adjustment is not working
properly.
Counter of the updated transaction is calculated based on Cost Adjustment
creation and not on the basis of updating
PriceDifferenceAdjustment flag = Yes
src/org/openbravo/costing/PriceDifferenceByDateProcess.java
src/org/openbravo/costing/PriceDifferenceProcess.java
Changes for Build #878
Naroa Iriarte <[email protected]> null
Fixed issue 28867:It isn't possible to create Menu Items from Widget
instances
At first it was possible to create a new menu item entry if the selected Widget
was a parent Widget,
but it was not possible if the current widget was an instance of a parent
Widget.
For example if you create a new entry in the Query/List widget it wold be
possible and it would show in
the Menu Item list of any instance of that Widget. But if you choose a concrete
widget which has a
superclass of the type Query/List, and create a new menu item, it would be not
possible to display it in the widget.
As it was interesting to be able to add a menu item at widget instance level,
the logic which handled this has been changed.
Now it takes into account if the instanciated widget has a menu item.
It is only possible to add functionality to those item menus with functions
defined in the OBWidget.js
modules/org.openbravo.client.myob/src/org/openbravo/client/myob/MyOBUtils.java
modules/org.openbravo.client.myob/web/org.openbravo.client.myob/js/ob-widget.js
Alvaro Ferraz <[email protected]> null
Fixes issue 29605: Foreign currency not setted in transaction
When creating a transaction manually from a payment, foreign currency, foreign
conversion rate and foreign amount fields were not setted to transaction. Now,
they will be setted as in TransactionDao.java, when the transaction is
automatically created from the payment.
modules/org.openbravo.advpaymentmngt/src/org/openbravo/advpaymentmngt/process/FIN_TransactionProcess.java
Last 20 lines of the console output:
[...truncated 20855 lines...]
Total time: 1 second
executing script 'Tomcat stop'
[int-basic-oracle] $ /bin/bash /tmp/build_step_template8886732729301724615.sh
ENABLE
DEBUG: Tomcat stop called with parameters: ENABLED=ENABLE
* Stopping Tomcat servlet engine for Openbravo tomcat
...done.
executing script 'Check log'
[int-basic-oracle] $ /bin/bash /tmp/build_step_template3972342056528789068.sh
ENABLE
DEBUG: Check log called with parameters: ENABLED=
Check log: openbravo.log is clean
Recording test results
Archiving artifacts
Checking \] ERROR|\] WARN
Email was triggered for: Fixed
Trigger Success was overridden by another trigger and will not send an email.
Sending email for trigger: Fixed
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Openbravo-builds mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-builds
