Difference between revisions of "Road Map"
(→Adempiere 4.2.0: See also section) |
(Added warning message) |
||
(35 intermediate revisions by 7 users not shown) | |||
Line 1: | Line 1: | ||
− | + | '''Warning: This is outdated information and needs to be corrected.''' | |
− | + | ||
− | + | ||
== Background == | == Background == | ||
− | The true origin of the | + | The true origin of the ADempiere Road Map is in the hundreds of requests for features, bugs and user developments that have been posted in the Compiere™ SourceForge forums in the last 5 years. This inventory of unresponded wishes quickly evolved into a development framework for the ADempiere project. |
In a furious debate started on September 1st 2006 and in just two weeks ([http://red1.org/forum/viewtopic.php?t=931 Read the historic debate]), an instantly created community not only decided on starting a fork, a product name, a basic structure for the project but also a short term roadmap for the project. | In a furious debate started on September 1st 2006 and in just two weeks ([http://red1.org/forum/viewtopic.php?t=931 Read the historic debate]), an instantly created community not only decided on starting a fork, a product name, a basic structure for the project but also a short term roadmap for the project. | ||
Line 12: | Line 10: | ||
− | '''Why | + | '''Why ADempiere?''' |
− | We chose | + | We chose ADempiere, making it the Open Source ERP/CRM/SCM of choice. |
* Truly stable, high performance, flexible, easy to use, facility of maintenance and scalability in the product application | * Truly stable, high performance, flexible, easy to use, facility of maintenance and scalability in the product application | ||
Line 48: | Line 46: | ||
* A useful application customisable for the individual business | * A useful application customisable for the individual business | ||
− | == | + | == ADempiere release strategy == |
− | + | ADempiere version numbers follow a longstanding tradition. Each version has three numbers, I.e., X.Y.Z. The "X" is only incremented when a really significant change happens, one that makes software written for one version no longer operate correctly on the other. The "Y" tells you which development "series" you are in. A stable version will always have an even number in this position, while a development version will always have an odd number. The "Z" specifies which exact version you have, and it is incremented on every release. | |
− | The development series is the code that the | + | The development series is the code that the ADempiere developers are actively working on, which is always available for public viewing, testing, and even use, although production use is not recommended! This is part of the "open source development" method. Eventually, the development series (i.e. 3.1.x) will become the stable one (i.e. 3.2.0) and a new stable series will then be established, and a new development series begun (i.e. 3.3.x). Or, if any really major changes happen, it might become 4.0.0 instead, and a 4.1.x series begun. |
− | == List of incomplete | + | == List of incomplete functionality that can be found in Adempiere menus: == |
{|{| border="1" cellpadding="5" cellspacing="0" | {|{| border="1" cellpadding="5" cellspacing="0" | ||
Line 63: | Line 61: | ||
!style="background:#efefef;" |'''''Sponsor''''' | !style="background:#efefef;" |'''''Sponsor''''' | ||
!style="background:#efefef;" |'''''Developer''''' | !style="background:#efefef;" |'''''Developer''''' | ||
+ | |-valign="top" | ||
+ | |- | ||
+ | |||
+ | |-valign="top" | ||
+ | |Online Help | ||
+ | |In Compiere 260a class OnlineHelp.Worker.run there is an incomplete implementation of online help, this is searching for links in the page with an attribute target=Online. | ||
+ | | | ||
+ | | | ||
+ | |-valign="top" | ||
+ | |- | ||
+ | |||
+ | |-valign="top" | ||
+ | |WAN profile connection | ||
+ | | | ||
+ | | | ||
+ | | | ||
|-valign="top" | |-valign="top" | ||
|- | |- | ||
Line 99: | Line 113: | ||
|-valign="top" | |-valign="top" | ||
− | |Drop Shipments | + | |[[Sponsored Development: Drop Ship|Drop Shipments]] |
|if you use this now it actually causes data corruption! | |if you use this now it actually causes data corruption! | ||
− | | | + | |[[idalica]] |
− | | | + | |[[idalica]] |
|-valign="top" | |-valign="top" | ||
|- | |- | ||
|-valign="top" | |-valign="top" | ||
− | |RMA | + | |[[RMA]] |
|Customer returns | |Customer returns | ||
− | | | + | |[[idalica]], [[El Salvador|'''Systemhaus Westfalia''']] |
− | | | + | |[[idalica]] |
|-valign="top" | |-valign="top" | ||
|- | |- | ||
Line 123: | Line 137: | ||
|-valign="top" | |-valign="top" | ||
− | |Replication | + | |[[Sponsored Development: Replication|Replication]] |
− | + | ||
− | | | + | |
| | | | ||
+ | |[http://e-evolution.com/ e-evolution] | ||
+ | |[[User:Trifonnt]] | ||
|-valign="top" | |-valign="top" | ||
|- | |- | ||
Line 200: | Line 214: | ||
| | | | ||
|-valign="top" | |-valign="top" | ||
+ | |Workbench | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |-valign="top" | ||
+ | |||
+ | |||
+ | |-valign="top" | ||
+ | |Custom Info Windows | ||
+ | |You can define your custom Info Windows (for search and select) from application dictionary (see tables AD_InfoWindow, AD_InfoColumn), but this is not working | ||
+ | | | ||
+ | | | ||
+ | |-valign="top" | ||
+ | |Organization Assigment | ||
+ | |You can assign a user to an organization for defined period of time | ||
+ | | | ||
+ | | | ||
+ | |||
|- | |- | ||
|} | |} | ||
− | '''''Special Note''''' : It was also mentioned in sourceforge forums the need of making a complete and serious security audit to | + | '''''Special Note''''' : It was also mentioned in sourceforge forums the need of making a complete and serious security audit to Adempiere. |
== New desired functionality == | == New desired functionality == | ||
Line 228: | Line 260: | ||
|-valign="top" | |-valign="top" | ||
− | | | + | |Serialization |
− | |The assets aspect is good but the creation and use of | + | |The assets aspect is good but the creation and use of serialized product makes it not very useful. You really need to be able to mass receive or ship. You also need to be able to put quantities other than one on the sales & invoice documents but have the shipment/receipt itemize which numbers! |
| | | | ||
| | | | ||
Line 278: | Line 310: | ||
|Customer Statement of Account | |Customer Statement of Account | ||
|Showing: previous balance, charges, credits, ending balance | |Showing: previous balance, charges, credits, ending balance | ||
+ | | | ||
+ | | | ||
+ | |-valign="top" | ||
+ | |- | ||
+ | |||
+ | |-valign="top" | ||
+ | |[[Sponsored Enhancement: Scan Inventory|Scan Inventory]] | ||
+ | |Tracks individual serial numbers | ||
+ | | | ||
+ | | | ||
+ | |-valign="top" | ||
+ | |- | ||
+ | |||
+ | |-valign="top" | ||
+ | |[[Sponsored Development: Promotions|Promotions]] | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |-valign="top" | ||
+ | |- | ||
+ | |||
+ | |-valign="top" | ||
+ | |[[Sponsored Development: Shipping Integration|Shipping Integration]] | ||
+ | |Add the ability to estimate and account for shipping charges. | ||
| | | | ||
| | | | ||
Line 285: | Line 341: | ||
|} | |} | ||
− | == | + | == ADempiere 3.1.0 == |
'''Goals''' | '''Goals''' | ||
Line 291: | Line 347: | ||
* Find and fix bugs | * Find and fix bugs | ||
− | * | + | * User interface improvement |
+ | |||
+ | * Run on 100% opensource stack | ||
'''Release would include the following components:''' | '''Release would include the following components:''' | ||
− | * Compiere | + | * Compiere 260a |
− | * | + | * Plugin and Migration Management. |
** Proposal: | ** Proposal: | ||
*** Create a Tool to do migrations based on XML Formats, so that version migration will be easier. | *** Create a Tool to do migrations based on XML Formats, so that version migration will be easier. | ||
− | *** Improve the tools created by Marco, Trifon | + | *** Improve the tools created by Marco, Trifon and Rob (ADCK, 2Pack) |
− | *** Use the | + | *** Use the Apache(http://db.apache.org/ddlutils/) DDLUtils libraries for this purpose. |
** Requirements | ** Requirements | ||
− | *** | + | *** Application Dictionary maintenance |
*** New version migration | *** New version migration | ||
*** New components integration | *** New components integration | ||
− | *** | + | *** Patch Management |
*** Export and Import the Data Dictionary | *** Export and Import the Data Dictionary | ||
*** Export and Import Entity Data (Client) | *** Export and Import Entity Data (Client) | ||
Line 319: | Line 377: | ||
* Oracle & Oracle XE | * Oracle & Oracle XE | ||
− | * Migration Script 253a to | + | * PostgreSQL support |
+ | |||
+ | * Migration Script 253a to 260a | ||
''' [http://sourceforge.net/pm/task.php?group_project_id=49235&group_id=176962&func=browse Adempiere Tasks ]''' | ''' [http://sourceforge.net/pm/task.php?group_project_id=49235&group_id=176962&func=browse Adempiere Tasks ]''' | ||
− | == | + | == ADempiere 3.2.0 == |
'''Goals''' | '''Goals''' | ||
− | * | + | * First stable release of the ADempiere 3.x series |
* Intensive Quality Assurance process | * Intensive Quality Assurance process | ||
+ | |||
+ | * Usability enhancement | ||
'''Release would include the following components:''' | '''Release would include the following components:''' | ||
− | * Compiere | + | * Compiere 260a |
− | * | + | * Plugin and Migration Management |
* Free PDF | * Free PDF | ||
Line 343: | Line 405: | ||
* Oracle & Oracle XE | * Oracle & Oracle XE | ||
+ | |||
+ | * PostgreSQL support | ||
* Migration Script 253a to 253b | * Migration Script 253a to 253b | ||
− | == | + | == ADempiere 3.3.0 == |
'''Goals''' | '''Goals''' | ||
− | * | + | * Manufacturing module |
+ | |||
+ | * Fixed Asset module | ||
+ | |||
+ | * POS module | ||
+ | |||
+ | * Fyracle support | ||
+ | |||
+ | * Web and Swing client enhancement | ||
'''Release would include the following components:''' | '''Release would include the following components:''' | ||
− | * Migration script Adempiere 3.2.0 to Adempiere 3.3.0 (Oracle,PostgreSQL, | + | * Migration script Adempiere 3.2.0 to Adempiere 3.3.0 (Oracle,PostgreSQL,Fyracle) |
− | * | + | * Fyracle support |
− | * Manufacturing | + | * Manufacturing module |
+ | * Fixed Asset module | ||
+ | * POS module | ||
− | == | + | == ADempiere 3.4.0 == |
'''Goals''' | '''Goals''' | ||
− | * | + | * All the goals stated in the 3.3 section |
+ | |||
+ | * Second stable release of the ADempiere 3.x series | ||
* Intensive Quality Assurance process | * Intensive Quality Assurance process | ||
Line 375: | Line 451: | ||
'''Release would include the following components:''' | '''Release would include the following components:''' | ||
− | * Migration script | + | * Migration script ADempiere 3.3.0 to ADempiere 3.4.0 (Oracle,PostgreSQL,MySQL) |
− | * | + | * Fyracle support |
− | * Manufacturing | + | * Manufacturing module |
− | == | + | * Fixed asset module |
+ | |||
+ | * POS module | ||
+ | |||
+ | == ADempiere 3.5.0 == | ||
'''Goals''' | '''Goals''' | ||
− | * | + | * Cash flow module |
− | + | * Human resource and payroll module | |
− | * | + | * Further client and usability enhancement |
− | * | + | * Reporting enhancement |
− | + | '''Release would include the following components:''' | |
− | * | + | * Migration script ADempiere 3.4.0 to ADempiere 3.5.0 |
+ | * Cash flow module | ||
+ | * Human resource and payroll module | ||
− | == | + | == ADempiere 3.6.0 == |
'''Goals''' | '''Goals''' | ||
− | * | + | * All the goals stated in the 3.5 section |
+ | |||
+ | * Last major release of the ADempiere 3.x series | ||
* Intesive Quality Assurance process | * Intesive Quality Assurance process | ||
Line 412: | Line 496: | ||
'''Release would include the following components:''' | '''Release would include the following components:''' | ||
− | * | + | * Cash flow module |
− | * | + | * Human resource and payroll module |
− | + | == ADempiere 3.99.0 == | |
+ | '''Goals''' | ||
− | + | * Migration to a modern, n-tier core | |
− | + | * AJAX Client | |
− | * | + | * New Reporting Engine |
+ | |||
+ | * Full database independence | ||
+ | |||
+ | * Security enhancement | ||
+ | |||
+ | * Performance improvement | ||
+ | |||
+ | * Test coverage | ||
'''Release would include the following components:''' | '''Release would include the following components:''' | ||
− | * New | + | * New Persistence engine |
** Proposal: | ** Proposal: | ||
− | *** To use | + | *** To use JPA compliant persistence engine [http://www.hibernate.org/299.html Hibernate EntityManager] or [http://www.oracle.com/technology/products/ias/toplink/jpa/index.html TopLink] Implementation |
** Requirements | ** Requirements | ||
− | *** | + | *** DB Independence (Supported Databases [http://www.hibernate.org/80.html Hibernate EntityManager] , [http://www.oracle.com/technology/products/ias/toplink/technical/support/database1013.html TopLink]) |
*** [http://developers.sun.com/learning/javaoneonline/2006/coreenterprise/TS-3395.pdf Better Persistency model] | *** [http://developers.sun.com/learning/javaoneonline/2006/coreenterprise/TS-3395.pdf Better Persistency model] | ||
*** [http://java.sun.com/javaee/overview/faq/persistence.jsp JPA Based on a Standard] | *** [http://java.sun.com/javaee/overview/faq/persistence.jsp JPA Based on a Standard] | ||
Line 440: | Line 533: | ||
*Business Rules Engine Integration | *Business Rules Engine Integration | ||
** Proposal: | ** Proposal: | ||
− | *** | + | *** [http://www.judoscript.com/articles/jsr223.html Java Standards JSR 223 Scripting APIs] i.e. [http://jakarta.apache.org/bsf/index.html BSF] & AOP. The use of a scripting language facilitates easy interaction with application components. Persistent class implement an inspector to validate if there is a Business Rule in the Application Dictionary. |
*** [http://developers.sun.com/learning/javaoneonline/2006/coreenterprise/TS-1365.pdf The AfterSave , BeforeSave , AfterDelete , BeforeDelete methods must be rewrited with Inspection classes.] | *** [http://developers.sun.com/learning/javaoneonline/2006/coreenterprise/TS-1365.pdf The AfterSave , BeforeSave , AfterDelete , BeforeDelete methods must be rewrited with Inspection classes.] | ||
** Requirements: | ** Requirements: | ||
Line 446: | Line 539: | ||
*** The Business Rule must be in the Application Dictionary. | *** The Business Rule must be in the Application Dictionary. | ||
− | * | + | *New Reporting Engine |
** Proposal | ** Proposal | ||
− | *** [http://superb-east.dl.sourceforge.net/sourceforge/pentaho/Pentaho_Report_Design_Wizard-1.2.0-RC2.pdf Integrate Pentaho Report Design Wizard] | + | *** [http://superb-east.dl.sourceforge.net/sourceforge/pentaho/Pentaho_Report_Design_Wizard-1.2.0-RC2.pdf Integrate Pentaho Report Design Wizard] |
− | *** [http://umn.dl.sourceforge.net/sourceforge/pentaho/Pentaho_Report_Designer_User_Guide-1.1.6.pdf | + | *** [http://umn.dl.sourceforge.net/sourceforge/pentaho/Pentaho_Report_Designer_User_Guide-1.1.6.pdf Design and customize report using Pentaho Report Designer] |
** Requirements: | ** Requirements: | ||
− | *** An easy to use | + | *** An easy to use User Interface |
− | *** | + | *** New Reports Wizard |
*** Drill Down & Drill Across | *** Drill Down & Drill Across | ||
*** Charts | *** Charts | ||
Line 458: | Line 551: | ||
*** A query language without creating views previously | *** A query language without creating views previously | ||
− | * | + | *AJAX Client [http://es.wikipedia.org/wiki/AJAX AJAX] |
** Proposal | ** Proposal | ||
− | *** We want to create a new user interface, Using AJAX technology the client will be communicated with the server using [http://en.wikipedia.org/wiki/SOAP SOAP] technology. | + | *** We want to create a new user interface, Using AJAX technology the client will be communicated with the server using [http://en.wikipedia.org/wiki/SOAP SOAP] or JSON technology. |
*** After reviewing a lot of AJAX solutions , we believe the best option is to use : | *** After reviewing a lot of AJAX solutions , we believe the best option is to use : | ||
**** [http://code.google.com/webtoolkit/ GWT Google Toolkit] [http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.UserInterface.WidgetGallery.html Widgets Gallery] [http://code.google.com/webtoolkit/documentation/examples/kitchensink/demo.html Demo] | **** [http://code.google.com/webtoolkit/ GWT Google Toolkit] [http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.UserInterface.WidgetGallery.html Widgets Gallery] [http://code.google.com/webtoolkit/documentation/examples/kitchensink/demo.html Demo] | ||
**** [http://www.nextapp.com/platform/echo2/echo/ Echo2] [http://demo.nextapp.com/Demo/app Demo] | **** [http://www.nextapp.com/platform/echo2/echo/ Echo2] [http://demo.nextapp.com/Demo/app Demo] | ||
**Requirements | **Requirements | ||
− | *** A User interface | + | *** A User interface that is attractive, intuitive and easy to use. |
− | + | ||
*** The client has to be really light | *** The client has to be really light | ||
− | *** Engine to build | + | *** Engine to build screens based on the AD |
*** Just get the information that the user is asking for | *** Just get the information that the user is asking for | ||
*** Capture high volume of data in a simple, multiple and mixed way. | *** Capture high volume of data in a simple, multiple and mixed way. | ||
− | *** Universal client (any internet browser | + | *** Universal client (any internet browser) |
− | + | ||
− | == | + | == ADempiere 4.0.0 == |
'''Goals''' | '''Goals''' | ||
− | * | + | * All of the goals stated in the 3.99 section |
− | * | + | * First stable release of ADempiere 4.x series |
+ | * Intensive Quality Assurance process | ||
Release would include the following components: | Release would include the following components: | ||
Line 488: | Line 580: | ||
[[Category:New features brainstorming]] | [[Category:New features brainstorming]] | ||
+ | [[Category:Development]] |
Latest revision as of 20:29, 4 September 2007
Warning: This is outdated information and needs to be corrected.
Contents
- 1 Background
- 2 ADempiere release strategy
- 3 List of incomplete functionality that can be found in Adempiere menus:
- 4 New desired functionality
- 5 ADempiere 3.1.0
- 6 ADempiere 3.2.0
- 7 ADempiere 3.3.0
- 8 ADempiere 3.4.0
- 9 ADempiere 3.5.0
- 10 ADempiere 3.6.0
- 11 ADempiere 3.99.0
- 12 ADempiere 4.0.0
- 13 See also
Background
The true origin of the ADempiere Road Map is in the hundreds of requests for features, bugs and user developments that have been posted in the Compiere™ SourceForge forums in the last 5 years. This inventory of unresponded wishes quickly evolved into a development framework for the ADempiere project.
In a furious debate started on September 1st 2006 and in just two weeks (Read the historic debate), an instantly created community not only decided on starting a fork, a product name, a basic structure for the project but also a short term roadmap for the project.
This roadmap as described aspires to strike a balance between rapidly releasing a version addressing some urgently required fixes and at the same time enhancing the functionality in such a way that it increases the perceived value of the solution. On the other hand, these very first releases would have to address the licensing of the precedent work from Compiere™ and some commercial components included in the original solution, namely the pdf library and the Oracle™ database.
Why ADempiere? We chose ADempiere, making it the Open Source ERP/CRM/SCM of choice.
- Truly stable, high performance, flexible, easy to use, facility of maintenance and scalability in the product application
- Expanding functionality footprint to be on par to other world class ERP solutions
- Technological jump from a client-server to a more modern, N-tier application
- User Interface which is easy to use, intuitive, attractive and well organized
- Collaboration of a real community where it is possible to integrate everyone's contributions and catalyse further development
- Tools to test, upgrade, migrate and apply bug corrections or source improvements
- Use of state-of-the-art open source tools
- To improve the product, based on the global user-community covering a myriad of verticals
- 100% Open Source, free of license supported by Open Documentation, Open Support and a not-for-profit ADempiere Council
What are the benefits?
- A better application for an exploding market
- A project with the right vision and better direction
- A road map clearly defined
- A real Community that is thriving and responsive
- A fast evolution of the product
- A useful application customisable for the individual business
ADempiere release strategy
ADempiere version numbers follow a longstanding tradition. Each version has three numbers, I.e., X.Y.Z. The "X" is only incremented when a really significant change happens, one that makes software written for one version no longer operate correctly on the other. The "Y" tells you which development "series" you are in. A stable version will always have an even number in this position, while a development version will always have an odd number. The "Z" specifies which exact version you have, and it is incremented on every release.
The development series is the code that the ADempiere developers are actively working on, which is always available for public viewing, testing, and even use, although production use is not recommended! This is part of the "open source development" method. Eventually, the development series (i.e. 3.1.x) will become the stable one (i.e. 3.2.0) and a new stable series will then be established, and a new development series begun (i.e. 3.3.x). Or, if any really major changes happen, it might become 4.0.0 instead, and a 4.1.x series begun.
Functionality | Description | Sponsor | Developer |
---|---|---|---|
Online Help | In Compiere 260a class OnlineHelp.Worker.run there is an incomplete implementation of online help, this is searching for links in the page with an attribute target=Online. | ||
WAN profile connection | |||
POS | |||
Substitute Product and Related Product | |||
Bank Statement Matcher | |||
Report View Column Replacement | |||
Drop Shipments | if you use this now it actually causes data corruption! | idalica | idalica |
RMA | Customer returns | idalica, Systemhaus Westfalia | idalica |
Replenishment of BOM | tries to buy BOM instead of parts | ||
Replication | e-evolution | User:Trifonnt | |
Purchase requisition approval | |||
Label Printer | functional in our project; lofx | ||
Bids | |||
Reservations (of stock) | aren't really reservations! | ||
Package Details on Shipments | do not seem to do anything.... of use anyway!? | ||
Withholding ? | I don't know if we must include it here. | ||
Knowledgebase | is not functional | ||
Unrealized gain and loss | not calculated using outstanding amount | ||
Some windows show the button "print" it actually just print an screenshot | Examples: info menus and view accounting application | ||
Workbench | |||
Custom Info Windows | You can define your custom Info Windows (for search and select) from application dictionary (see tables AD_InfoWindow, AD_InfoColumn), but this is not working | ||
Organization Assigment | You can assign a user to an organization for defined period of time |
Special Note : It was also mentioned in sourceforge forums the need of making a complete and serious security audit to Adempiere.
New desired functionality
Functionality | Description | Sponsor | Developer |
---|---|---|---|
Request e-mail collector | |||
Serialization | The assets aspect is good but the creation and use of serialized product makes it not very useful. You really need to be able to mass receive or ship. You also need to be able to put quantities other than one on the sales & invoice documents but have the shipment/receipt itemize which numbers! | ||
UOM opposite conversion | The conversion - units of measure and currency too are very messy to setup... once one conversion is defined the opposites should be automatic. | ||
Warehouse Location | Not missing functionality, but it works great to create virtual warehouses within a main warehouse ... but as a "bin" within a warehouse it doesn't strike me as particularily useful! | ||
Standard reports | That businesses use be available as default in ADempiere. Probably localization subprojects, standard reports can be different in each country. | ||
Year end closing | Income summary and retained earning is setup but not use | ||
Fixed Asset | |||
Customer Statement of Account | Showing: previous balance, charges, credits, ending balance | ||
Scan Inventory | Tracks individual serial numbers | ||
Promotions | |||
Shipping Integration | Add the ability to estimate and account for shipping charges. |
ADempiere 3.1.0
Goals
- Find and fix bugs
- User interface improvement
- Run on 100% opensource stack
Release would include the following components:
- Compiere 260a
- Plugin and Migration Management.
- Proposal:
- Create a Tool to do migrations based on XML Formats, so that version migration will be easier.
- Improve the tools created by Marco, Trifon and Rob (ADCK, 2Pack)
- Use the Apache(http://db.apache.org/ddlutils/) DDLUtils libraries for this purpose.
- Requirements
- Application Dictionary maintenance
- New version migration
- New components integration
- Patch Management
- Export and Import the Data Dictionary
- Export and Import Entity Data (Client)
- Delete entities (Client)
- Wizard to create new windows
- Proposal:
- Free PDF
- Jasper Report integration
- Oracle & Oracle XE
- PostgreSQL support
- Migration Script 253a to 260a
ADempiere 3.2.0
Goals
- First stable release of the ADempiere 3.x series
- Intensive Quality Assurance process
- Usability enhancement
Release would include the following components:
- Compiere 260a
- Plugin and Migration Management
- Free PDF
- Jasper Report integration
- Oracle & Oracle XE
- PostgreSQL support
- Migration Script 253a to 253b
ADempiere 3.3.0
Goals
- Manufacturing module
- Fixed Asset module
- POS module
- Fyracle support
- Web and Swing client enhancement
Release would include the following components:
- Migration script Adempiere 3.2.0 to Adempiere 3.3.0 (Oracle,PostgreSQL,Fyracle)
- Fyracle support
- Manufacturing module
- Fixed Asset module
- POS module
ADempiere 3.4.0
Goals
- All the goals stated in the 3.3 section
- Second stable release of the ADempiere 3.x series
- Intensive Quality Assurance process
Release would include the following components:
- Migration script ADempiere 3.3.0 to ADempiere 3.4.0 (Oracle,PostgreSQL,MySQL)
- Fyracle support
- Manufacturing module
- Fixed asset module
- POS module
ADempiere 3.5.0
Goals
- Cash flow module
- Human resource and payroll module
- Further client and usability enhancement
- Reporting enhancement
Release would include the following components:
- Migration script ADempiere 3.4.0 to ADempiere 3.5.0
- Cash flow module
- Human resource and payroll module
ADempiere 3.6.0
Goals
- All the goals stated in the 3.5 section
- Last major release of the ADempiere 3.x series
- Intesive Quality Assurance process
Release would include the following components:
- Cash flow module
- Human resource and payroll module
ADempiere 3.99.0
Goals
- Migration to a modern, n-tier core
- AJAX Client
- New Reporting Engine
- Full database independence
- Security enhancement
- Performance improvement
- Test coverage
Release would include the following components:
- New Persistence engine
- Proposal:
- To use JPA compliant persistence engine Hibernate EntityManager or TopLink Implementation
- Requirements
- DB Independence (Supported Databases Hibernate EntityManager , TopLink)
- Better Persistency model
- JPA Based on a Standard
- Powerful query language
- Impact in the speed of the development
- Increase in the Performance via cache
- Proposal:
- Business Rules Engine Integration
- Proposal:
- Java Standards JSR 223 Scripting APIs i.e. BSF & AOP. The use of a scripting language facilitates easy interaction with application components. Persistent class implement an inspector to validate if there is a Business Rule in the Application Dictionary.
- The AfterSave , BeforeSave , AfterDelete , BeforeDelete methods must be rewrited with Inspection classes.
- Requirements:
- Modify the Business Logic without changes in the source code, and online.
- The Business Rule must be in the Application Dictionary.
- Proposal:
- New Reporting Engine
- Proposal
- Requirements:
- An easy to use User Interface
- New Reports Wizard
- Drill Down & Drill Across
- Charts
- Export reports to several formats (HTML,PDF,OpenOffice)
- A query language without creating views previously
- AJAX Client AJAX
- Proposal
- We want to create a new user interface, Using AJAX technology the client will be communicated with the server using SOAP or JSON technology.
- After reviewing a lot of AJAX solutions , we believe the best option is to use :
- Requirements
- A User interface that is attractive, intuitive and easy to use.
- The client has to be really light
- Engine to build screens based on the AD
- Just get the information that the user is asking for
- Capture high volume of data in a simple, multiple and mixed way.
- Universal client (any internet browser)
- Proposal
ADempiere 4.0.0
Goals
- All of the goals stated in the 3.99 section
- First stable release of ADempiere 4.x series
- Intensive Quality Assurance process
Release would include the following components: