Understanding Orderables, TradeItems, and CommodityTypes
In order to present the example configuration for valid destinations and valid sources, the exemplar facility types and facility codes are presented below:
In this example there are three facility types (Clinic, Private Hospital and Warehouse) and six facilities of each type.
Valid Destinations table, apart from program code, consists of facilityTypeCode and destination columns.
In facilityTypeCode column there should be all codes of facility types which are able to supply other facilities. In destination column there should be facility codes of facilities which are supplied by a facility of type indicated in facilityTypeCode column.
The Valid Destinations table for these configuration is created below:
Valid Sources table, apart from program code, consists of facilityTypeCode and facilityCode/organizationName.
In facilityTypeCode column there should be all codes of facility types which are to be supplied by warehouses or organizations.
In facilityCode column there should be codes of facilities which supply other facilities. Most often it will be a warehouse.
In organizationName column there should be a name of a supplying organization if there is such.
The Valid Sources table for these configuration is created below:
In the table there are warehouses’ facility codes (FAC03, FAC06) in the facilityCode column. It means that these facilities supply facilities of privC and privH facility types.
Setup Supervisory Nodes, Requisition Groups, Supply Lines
To download the catalog template CSV, go to CCE Management > CCE Catalog. Click "Download current catalog." This will download a CSV file that can be used as a template for your CCE Catalog. If you already have an Excel or CSV file of a CCE Catalog that you'd like to use, you must transfer the data into the OpenLMIS CCE Catalog template. You must retain the same column headers from the downloaded catalog template. If you delete or change any column headers in the template, you will not be able to upload the CSV as your new CCE Catalog.
Setup Google Analytics tracking
OpenLMIS integrates with Google Analytics in order to provide insights into platform traffic and user behaviour. In order to benefit from this integration, start with creating a Google Analytics account here: https://analytics.google.com/analytics/web. Once that's done, you should find your Google Analytics tracking code. Go to Admin settings on Google Analytics and find section called "Tracking Info". This section will show your unique Tracking ID as shown below.
The Tracking ID needs to be provided to your UI project (equivalent of https://github.com/OpenLMIS/openlmis-reference-ui) during build time. It can be achieved in two ways:
- Setting the ANALYTICS_TRACKING_ID property to your Tracking ID in your config.json file
- Setting environment variable ANALYTICS_TRACKING_ID to your Tracking ID during your UI build
Once built and deployed to your server, the tracking should be in place. and you should be able to see the metrics in the Google Analytics account you created. For any issues with Google Analytics, you can check their help center: https://support.google.com/analytics
In addition to the regular metrics in place, the OpenLMIS instance will also send button click events to the Google Analytics. You can also implement and send your own events. The UI in the offline mode will collect the page views and events and send them as soon as the instance is back online.
Step 3: Configuration via CSV uploads