Skip to main content

Posts

Showing posts with the label Message box in ADempiere

Popup Message from Server to Clients using Socket Programming in Adempiere

It will be more convenient for the client if he get a popup notification at the time of order completion. We achieved this using Socket Programming in ADempiere. In Socket Programming, messages sends through ports using port number. The message send from the server is identified by the client port and given to a popup window. A column named IsNotified added to AD_Session Table and it’s value is set to ' Y'  by default . When an order is completed, this column value will change to ' N' . Clients with IsNotified value 'N' will get the popup notification. The popup will open in every minute and elapse automatically after 10 seconds until the client closes it manually. This time IsNotified column value will change to 'Y'. So that particular client won’t get any popup notification further. The following classes added to ADempiere: •         org.compiere.process.Notifier.java •         org.compiere.process.PopupClient.java

Message box in ADempiere ERP

ADempiere have its own standard in its pop up messages. Normally we can use JOptionPane provided by  java. But you need to compromise its look and feel in your application. The following are the commonly used pop up box menthods in ADempiere in different instances. 1. mTab.fireDataStatusEEvent("Already open access","message",true); Used in callouts. 2. log.saveError("Invalid Date", message); Used in model classes. 3. ADialog.error(m_WindowNo, this, "FillMandatory", sb.toString());             return false; Used in client classes. If it is used in the higher build priority classes, you may have build error. 4. throw new IllegalStateException("Could not create accrual entry"); Used to throw exceptions in your code.

Adempiere Schema Diagram

From the below mentioned link, you may get the entire table schema in adempiere. http://globalqss.com/idempiere/1.0c/schemaspy/MaterialManagement/relationships.html