There is another preference which controls how masterdata is loaded: Masterdata models batch size.
OPENBRAVO WEB POS FULL
If this preference is set to 'Y', no refresh will happen during login unless it is time to do a full or incremental. Time to incrementally refresh masterdata (in minutes): This field controls how frequently should an incremental refresh be done.Īdditionally, since 17Q2.4, there is a preference called No Auto Incremental Load at Login.Full refresh only happens on login it will never happen while the user is logged in, as depending on the dataset size, it may take a significant amount of time. Time to fully refresh masterdata (in minutes): This field controls how frequently should a full refresh be done.There are two fields on POS Terminal Type window which control this functionality: Incremental refresh is in most cases much less demanding on the server, and also much quicker if the amount of changes in the data is not big. Additionally, also depending on the system configuration, an incremental refresh will automatically and periodically happen while the user is logged in the system. This should be considered installation of the system, and it is mandatory.Īfter that, subsequent logins will do a full or incremental refresh depending on the system configuration. When first accessing the Web POS from a device, a full refresh is always triggered. Incremental refresh: this mode loads only the records which have changed since the last refresh, and inserts (or updates) them in the database.Full refresh: this mode loads every record of each model, and inserts it in the local database.There are two ways to load the masterdata in the Web POS: This document will explain the second type, as it is a bit more complex, due to the fact that it is in most cases big, and cannot always be loaded in full and in one shot. Masterdata models: products, business partners, discounts, taxes.Terminal configuration related data: This information is retrieved using a single request to the backend (.term.Terminal request), and it is always retrieved in full every login or page refresh.In order for the WebPOS to be able to keep working when the connection is unstable or it is not possible to reach the server, it is necessary to load a group of key data information. 3.2 Masterdata models not defined in Retail Pack for POS.3.1 Masterdata models defined in Retail Pack for POS.3 Appendix: Masterdata models of Retail WebPOS.2.4 Monitoring masterdata refresh across terminals.2.3 Technical implementation of masterdata loading.The Web service is located in /.posterminal.jsonrest context, and queries are writen in JSON format and use the HTTP method POST. The POS JSON Web service allows to execute HQL queries to retreive data from Openbravo entities. The Advanced REST client application offers a convenient way of testing and executing the POS JSON Web Services, Allowing to execute, inspect the JSON results properly formated, save requests, etc. In this document we use the Advanced REST client Application that runs on top of the Google Chrome web browser and can be installed from the Chrome Web Store. To test JSON Web Services there are multiple options that provide an easy way to execute JSON Web Services.
All the generic sections in that document like, Login and Security, Error result, Conversion from and to JSON, are common in both implementations. The POS JSON Web Services are based on the JSON REST Web Services. Althought its focus on the Openbravo POS Terminal Client, these web services are generic and can be used for other clients or integration processes. The POS JSON Web Services are a collection of JSON Web Services for Openbravo focused to provide access to data and business logic for Point of Sale terminals.