The original article was created by Andries L Pretorius on June 2010 at Open Source.
In this article on advanced aspects of Compiere by Andries L Pretorius, author of Compiere 3 Implementation Guide, we will cover:
- Overview of the Compiere Application Dictionary and its components
- Adding a custom field in Compiere
- Setting up a basic document process approval workflow in Compiere
The Compiere Application Dictionary (AD)
The Application Dictionary makes Compiere a truly unique and flexible business framework. Compiere was originally designed from the ground up on a model driven architecture (MDA), as defined by the Object Management Group (OMG). The system design conforms to an open standard in its layered architecture between business, application, and platform logic. MDA separates the business logic modeling, from technology modeling so as to ensure that both can evolve within their own domains, but still keeping within a framework of an open standard (and platform independent) that interconnects the two.
The benefit in the Compiere environment is that through modeling, design, and build the actual deployment time is greatly reduced. The AD also ensures a seamless upgrade of the platform while having little impact on the environment-specific business objects and processes.
The Application Dictionary of Compiere is meta data driven, meaning that contextual data defines the experience. This also means that the end user presentation layer and thus, the Graphical User Interface (GUI) platform have been defined in different technologies (i.e. Java Swing, HTML, and Ajax) and offers endless possibilities.
The Application Dictionaries can be illustrated as shown in:
[singlepic id=267 w=320 h=240 float=center]
To access the Application Dictionary you need to log in as a System Administrator and refer to the sub menu shown in:
We will use the Java Swing (Compiere Standard Edition) user interface for illustration purposes in this section.
[singlepic id=268 w=320 h=240 float=center]