...
Burti API is not included in Standard ERP base package. You will need to acquire a license from us and as soon as the formalities are settled, you will be provided with the API module package and an enabler key file. These are files that you will need to place on your server. You likely do not need to read ahead, since typically we will do these steps for you. In this case skip ahead to the next section.
Contents of the package:
| File | Description |
|---|---|
Burti Enabler - Enables Burti package functionality | |
| |
| If you are already using any Burti functionality packages, you will likely already have this installed. |
halcust/datadefEN.hal |
Support file. You must amend your
| ||
halcust/enab/... files |
| These files need to be added to your HAL Rules setting and distributed to client computers. These will add UI elements that will allow you to renew Burti Enabler keys from your SERP client if necessary. | |||
Burti API package | |||
hobcust/JSON.hob | |||
halcust/datadefJSON.hal | Support file. You must amend your
| ||
halcust/json/... files | These files need to be added to your HAL Rules setting and distributed to client computers. These will add UI elements that will allow you to configure the Burti API functionality. | ||
| These will most likely be empty folders at first but will be populated by support files generated by the package. These will provide the main functionality of the API. | ||
Enabler key file | |||
BurtiEnabler.bkey | This file contains the product key that enables the use of the package. This will need to be updated periodically with a new key. However, this is done automatically in most cases and you will likely not need to bother with this. The contents of this file can also be manipulated via the Burti Enabler package mentioned at the top of this table. | ||
Setting up
Burti API package and product enabler key
...