Release Notes/3.0PR14Q3
Contents |
Openbravo ERP Platform 3.0 PR14Q3 available
Release date: August 6th, 2014
Module version: 3.0.24005
Check out what's new, fixed issues and frequently asked questions about the latest release of Openbravo. As always, you are encouraged to tell us what you think, by raising an issue in issues.openbravo.com or by discussing it in the Open discussion forum.
What's New
 | Starting from this PR14Q3 release Openbravo does no longer support PostgreSQL 8.3.x and Oracle 10. The full list of System Requirements can be seen here. |
Standard UI Process Definition. Parameter Windows. Phase III: New Parameter Windows capabilities:
- Support for multiple grid parameters
- Client side callouts for parameters
- JavaScript load actions executed when the window is rendered allowing to implement complex logic in client side based on default parameters
- JavaScript pre actions which are executed before invoking backend process, they allow to do client side validations and data transformations before the process is executed
- HQL based tables: Capability to define read only datasources based on an HQL instead of in a DB table/view. Filtering and sorting capabilities are provided by the platform without the need of extra coding. These datasources are aimed to be used in Standard and Parameter Windows.
- Infrastructure to write jUnit test for requests: Infrastructure to write jUnit test for requests. It allows to create unit tests for testing requests within an Openbravo session.
- Tree Extension Improvements: Implements the following new features for Advanced Trees:
- Define read only tree at tab level
- Support different deletion policies for parent nodes (prevent deletion or reparent children)
- Default Tree View Logic: defines a logic to decide wether Tree or Grid view should be shown by default
- Support Saved Views: allows to save a tree view
- Support for 12 hour time format: Support to visualize in UI time fields formatted in 12 hour system (appending AM/PM)
- Open Balances: Ability to browse open balances for AR and AP in the General Ledger
Performance improvements
- Improved AP&AR Screens. Phase I.: Redesign of the Add Payment windows to be based on the Parameter Windows for better performance and extensibility
- Windows Loading Optimization. Phase II: Improved the time and resources consumed in client side to load generated windows. Grid fields in client side are lazily loaded, so only the ones that are opened are loaded.
- Implement 2.50 drop down list references in 3.0 style: Currently 2.50 drop down list references (table and tableDir) are implemented as they were in 2.50. This is, the complete list of possible values is returned on load. This affects performance in case of big volumes. This project aims to implement these references in 3.0 style, not returning the whole set of values but dynamically request to backend for them.
Fixed issues
- 26487: update.database rebuilds unchanged tables (Oracle, charset UTF8)
- 26846: improved live sessions checks on tomcat restart to work with load balanced servers
- 26645: Tables and Tabledirs are not working in Internet Explorer 7 and 9
- 25985: P&E smarclient datasources are leaked
- 26012: Rich Text Fields are always placed in a new line
- 26820: Unexpected behavior using an obuisel_selector reference with the id as display field
- 26817: In Financial Account window, autosave is wrongly triggered while navigating with keyboard
- 26684: Alert datasource has no pagination
- 26838: Unpaged request in Financial Account Transaction
- 24848: "Closed period" verification should not be performed when trying to process a document not configured to generate accounting
- 25817: When Background Acct Server process is run with "system administrator" role it does not consider exchange rate at doc level
- 25886: When posting a payment using credit and multi-currency, Bank Revaluation Gain and Loss Accounts are used at the same time
- 26242: Orders could be reactivated although they have a related payment if it is not paid
- 26467: Wrong Transaction's accounting entry when working with multi-currency and cash vat functionality
- 26493: Should not be possible to Reactivate an old Reconciliation when Financial Account is defined as manual reconciliation
- 26503: When trying to post a Physical Inventory with total cost = 0, Post status should be "Disabled for Accounting"
- 26571: Error when paying a "cash vat" invoice with total amount lower than related order's amount
- 25893: the warehouse does not fit with the organization in the Return Material receipt window
- 26823: the transaction cost of the Valued Stock report should be filtered regarding the movement date
Check the complete list of fixed issues and API changes.
Known issues
- It has been reported that in some cases the rebuild process requires more RAM memory. It is recommended to run the virtual appliances with at least 1.5GB of RAM.
- 16452: On Windows Openbravo won't start if the installation path contains a space
- 27039: Login fields are now filled and remembered by Chrome and Internet Explorer
- The redesign of the Add Payment window might require a few adaptations in any previous customization using that functionality. In particular, the new process takes advantage of the possibility of implementing directly in Java: the default values, the read only logic and the display logic. It is not recommended to use the old Add Payment process, as it is not going to be maintained anymore. Instead you should be migrating your customizations to the new process definition.
If any custom code runs the Add Payment process (or any other process defined in the Process Definition window), you might be required to implement the Java code for your customized window only if the process doesn't work properly. The fastest way to do it is to create the Java classes that extend from the original classes in Openbravo. In your new classes you just need to add the following annotation just on top of the class definition, entering the ID of the customized window that is running the Add Payment process (take a look at the way it's defined in the original classes): @ComponentProvider.Qualifier("<WINDOW ID>"). For example, if the Add Payment process is called from a customized window cloned from the Sales Invoice window, then you need to create 3 new classes in your module extending the Openbravo's classes: SalesInvoiceAddPaymentDefaultValues.java, SalesInvoiceAddPaymentDisplayLogics.java and SalesInvoiceAddPaymentReadOnlyLogics.java. Example:
@ComponentProvider.Qualifier("B794DF2B11E14643AA8BD5511277FF4D") public class SalesInvoiceAddPaymentDefaultValuesCopy extends SalesInvoiceAddPaymentDefaultValues {}
Additionally, and depending on the business scenarios in your customization, you might need to override on your own classes any of the public methods available in the Openbravo's classes.
Extensions
There is a vast array of modules that extend the functionality of the Openbravo ERP Platform. These include Extensions, Connectors, Localizations, Vertical and Horizontal Solutions, and Tools.
During this release following modules were created / updated:
Improved Invoice Payment Report: Performance improvement in the Invoice Payment Report that leverages Open Balances Development
Please discover the full range of modular extensions in the Openbravo Forge (use the filter option to filter by Module Name), with an easy-to-browse catalog of commercial modules available in Openbravo Exchange.
Download Details
Please evaluate the Openbravo ERP Platform System Requirements, prior to download.
In order to download the Openbravo ERP Platform, please visit downloads.openbravo.com.
Online Demo
We have set up our online demo so that it is easier for you to test the 3.0 PR14Q3 release. Select the Country and the language to log in. Check it out!
Trial License
If you want to experience the full power of the Openbravo ERP Platform and test some of its commercial modules in your own environment ask for a free 30-day trial subscription.
Installation & Updates
| | Starting with 3.0MP21 version the Openbravo Appliance is based on the Ubuntu Server operating system. |
To install the Openbravo ERP Platform, please follow the Installation Manual.
To update the Openbravo ERP Platform, please follow the Updates and Upgrades Manual.
| | All releases are published in the QA Approved maturity status and they are promoted to Confirmed Stable status after 2 month. The current maturity status of this release can be seen above and in this page. |
Other resources and links
- Get information about previous releases in the Release History page.
- Learn more about the open source Openbravo project
Special thanks
Finally, we give our thanks to the Openbravo Community which continues to support us with their valuable time and knowledge.
We also thank all Openbravo users for making Openbravo a huge success.