Scribd
Upload
113 views

09 Application Dictionary

The document discusses the application dictionary framework in ADempiere and how to create a new field in the sales order window using the application dictionary. It describes creating a new column in the database table, creating the field in the window, making it a dropdown of users, and only visible for POS orders. The changes are then packaged and deployed to another system using the packout and packin tools.

Uploaded by

hans09
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
113 views

09 Application Dictionary

The document discusses the application dictionary framework in ADempiere and how to create a new field in the sales order window using the application dictionary. It describes creating a new column in the database table, creating the field in the window, making it a dropdown of users, and only visible for POS orders. The changes are then packaged and deployed to another system using the packout and packin tools.

Uploaded by

hans09
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Module 9

Introduction to
Application Dictionary
By Kitti Upariphutthiphong
Technical Consultant, ecosoft
[email protected]

ADempiere|ERP
1

Module Objectives
ADempiere as an Application Framework
Knowing Application Dictionary

Creating a new simple window using Application Dictionary

ADempiere as an Application Framework

ADempiere is well known for its


Powerful Application

Dictionary Framework

Planning &
Configuration

Coding
This is a Big topic that require time to study, yet Worth It!
3

Application Dictionary Framework

ADempeire Application Architecture


Interface Layer
Pure Application Dictionary
Pure Configuration
Note: Tab = Table, Field = Column

Process Callout Layer


Partly managed by
Application Dictionary
Configuration + Coding
Java Code or Light Weight Script

Document / Data Model Layer


Object Model
Pure Java Coding
Base infrastructure of the system
5

Application Dictionary Development Scenario

Configure
Database Table
Create & Update
Table, Columns
Syncing changes to
underlining DB

Develop Process
& Reports
(Coding)
Additional Callout or
Process attached to
Fields, Buttons or
Actions
Require Java or Light
Weight Scripts

Windows, Tab,
Fields, Buttons
Create & Update
Windows, Fields,
Buttons
Organize looks and
feels

Package as 2Pack
(PackOut)
Package all changes
as XML package
For distribution to
target server

Reference Data
Fields
Reference fields to
data source
Smart Database
lookup

Add Rules &


Logics to Fields
Add field logics
How data and fields
will display
Fields dependencies,
etc.

Production
Deployment
(PackIn)
Deployment
Management

WORKSHOP

Scenario
For the POS Order only, we want a new field Walkin
Buyer Name that list all user in the system
This field will display only when it is a POS Order, when it
display, display as mandatory field!

Create a new simple field in Sales Order window


Create new WalkinBuyer Column in table Back to Table and Column window
C_Order
Create new column with

Login as System Administrator


Open Table and Column window
Lookup for DB Table Name = C_Order
With record C_Order selects, click on
Column tab
Click New
We need to create new WalkinBuyer
element first, as this does not exists.
Right click on System Element field, and
click Zoom

DB Column Name: WalkinBuyer


System Element: WalkinBuyer
Name: Walkin Buyer Name
Reference: String
Length: 22

Click Save

Sync with Backend Database to create new


column
Click on Synchronize Column button to
auto create new Column in DB.

Element window open

Create new WalkinBuyer element in


Element window
Click New
DB Column Name: WalkinBuyer
Name: WalkinBuyer
Print Text: Walkin Buyer Name

Click Save

Clicking Synchronize Column button will sync the


Dictionary in ADempiere to the backend database. If the
table exist (like in this case), it will just alter table. But if the
table do not exists, it will create a new table.
9

Create a new simple field in Sales Order window


Create the new field in Window Sales Order

Open Window, Tab & Field window


Lookup for Name = Sales Orders
With record Sales Order selects, click on Tab tab
Lookup for Tab Name = Order
Expand the page and scroll down
Click Create Fields button
New fields will be created,

On the right pane, select Walkin Buyer Name and


move it to up under the field Self Service

Click Field Tab, lookup for Field = Walkin Buyer


Name
The new field is already in this Sales Order window

View new field in Sales Order window.

Note that system will create all fields that has not
been created before. Walkin Buyer Name field is
one of them.

Logoff and Login again as GardenWorld Admin.


On Sales Order window, you will see the new
Walkin Buyer Name field.

Arrange the new field.


Click on Field Sequence tab
Select new fields and move to the left pane. Except
the Walkin Buyer Name field which remain on the
right pane.
10

Adding some rules to the field

So far, we have just create a simple string field. Now we


will continue by making this field a user name dropdown
list. And make it required field only when Target Document
Type is POS Order

Make WalkinBuyer field reference to user list in


table AD_User

Re-Login as System Administrator


Open Table and Column window
Lookup for DB Table Name = C_Order
With record C_Order selects, click on Column tab
Look for column WalkinBuyer and change the
setting as follow,

Make the setting as follow,


Display Logic: @C_DocTypeTarget_ID@=135
Mandatory Overwrite: Yes

Save change

View new field in Sales Order window.


Logoff and Login again as GardenWorld Admin.
On Sales Order window, you will see the new
Walkin Buyer Name field now as drop down list.
By changing the Target Document Type to POS
Order, it will be Visible and mandatory.

Reference: Table
Reference Key: AD_User

Save change
Click on Synchronize Column button to auto
update Column in DB.

Make this WalkinBuyer field visible only when


Target Document Type is POS Order

Open Window, Tab & Field window


Next step, we will package the changes as 2Pack
Lookup for Name = Sales Orders
format for reuse.
With record Sales Order selects, click on Tab tab
Lookup for Name = Order
Expand the page and scroll down to Walking Buyer
Name field.
11

Package the changes with 2Pack - Packout


Package the change using Packout
Re-Login as System Administrator
Open Packout window
Click New,

Name of Package: MyFirstPackout


Package Version: 1.0
Registered Email: [email protected]
Email Address: [email protected]
Creation Directory: C:\Packout
Version: Release No: No specific release
Description of Package: .
Instruction: -

Click on Package Details tab


Click New,
Type: Application or Module
Menu: Sales Order
Note: -

Click Save
Back to Export Package tab,
Click Export Package button

A package called MyFirstPackout will be


created under C:\Packout

Package will be in zip for Windows and


tar.gz for Linux. Inside package is instruction
on all the change we made in XML format.
We can use this package to deploy the
changes in Production System.
Click Save
12

Deploy the change to Other System - Packin


Deploy the change to Other System using
Packin
In target system, login as System
Administrator
Open Packin window
Click New,
Package Source Type: File
Package Source:
C:\Packout\MyFirstPackout.zip
Package Directory: migration

Click Save
Click PackIn button to deploy
If no error, OK message will be shown on
the bottom left of the window.

In Target System, view new field in Sales


Order window.
Logoff and Login again as GardenWorld
Admin.
On Sales Order window, you should see the
new Walkin Buyer Name field.

2Pack is a good way of packaging and deploying


application. With Package Maintenance and
Package Installed windows, you can also monitor
changes you have make in a centralized way.
So far we only touch on the basic feature of
Application Dictionary. To be an expert, you
need a lot of real life experiences.
13

You might also like