Status: Production
--
-
- The Release 2.5.3c is available for download
-
-
-
- Detail change log via CVS, SourceForge and Partner Forum -
- CVS Head is R2.5.3c -
- - Known issues (see also: Status and Known Issues) -
- Migration is available -
- Restrictions
-
-
-
- Status: Beta (You can Enable Beta Functionality on Client level) for
-
-
-
- HTML UI -
- POS -
- BOM (new structure) -
- - Status: Limited Production
-
-
-
- Costing -
-
- - Status: Beta (You can Enable Beta Functionality on Client level) for
-
- Check the Upgrade notes below if applicable -
New Features
-Functionality
--
-
- Cash Based Accounting (2.5.3a) -
- Commitment/Encumbrance Accounting (2.5.3a) -
- Reporting with multiple hierarchies (2.5.3a) -
- Import Price Lists (2.5.3a) -
- Improved Mullti-Org functionality for optionally shared entities (2.5.3b) -
- Print Barcodes (2.3.5c) -
- Collaboration Chat & Content Management (2.3.5c) -
Technology
--
-
- Connection Profile with management via role/user (2.5.3b) -
- Workflow action "email" (2.5.3b) -
- Web Store UI Improcement (2.3.5c) -
Closed Bugs, Feature Requests
--
-
- See closed Bugs and PreRelease Bugs as well as closed Enhancements -
Planned Functionality and Development Priorities
--
-
- Check the current list of Open Items . Planned Functionality and Priorities are determined by Adempiere Partners . -
Optional Services
--
-
- Data Migration -
- Technical and Functional Intensive Training -
- Online Training -
Upgrade Notes
-Release 2.5.3 requires Java 1.5 and requires that you delete the jboss directory before you extract the files.
-When upgrading from a previous release, you need to execute RUN_setup and RUN_Migrate (in that order).
-Database Name: From Oracle "SID" to Service Name
-For Oracle, Release 2.5.2 uses the Service Name - previous releases used the SID - to connect to the database. The Global Service Name is discovered by RUN_setup and is usually in the form of <instance>.<domain> - example "adempiere.myCompany.com". The Service Name is defined when installing the database.
-When manually entering the Database Name (e.g. in the Connection Dialog) make sure that you enter the Service Name.
-