Implemented for configurations:

• BAS Accounting, version 2.2;
• BAS Small business;
• UNF. Management of a small firm;
• UTP. Trade enterprise management.

Fig. 1. Scheme of exchange with SalesDrive.

How implemented:

Based on the exchange scheme (Fig. 1), an order (request) in SalesDrive can be created both manually in SalesDrive and received when exchanging with the site. But part B will work the same in any of these options.

Integration functionality includes:

1. Receiving an order/pre-order via WebHook. 

When an order is created or its status changed, SalesDrive sends a message with the order data. On the BAS side, it is received by the HTTP service.

Result:

а) An order is created/changed and its status in BAS;

б) Sent (using the API) to SalesDrive the number of the created document (If allowed by the corresponding setting).

2. When an order status is changed in BAS, the status value is sent to SalesDrive (using the API) (If allowed by the corresponding setting)

3. Since the SalesDrive API does not imply changing the amount of the order, when changing the amount of an order/pre-order in BAS, the line "Respect for changing the amount of the order - 0000.00 UAH" is added to the order comment in BAS. and the comment value (via API) is sent to SalesDrive.

Fig. 2. SalesDrive integration settings.

Integration settings specify authorization parameters for working with API (Account and API key).

 

Fig. 3. How to find Account and API Key parameters (1).

Fig. 4. How to find the Account and API Key parameters (2).

To receive a Webhook, you need to publish an HTTP integration service (called SalesDrive) and perform port forwarding.

The result should be a URL like this:

http://<external IP>:<port>/<public name>/hs/SalesDrive/WebHook

It must be specified in the Webhook SalesDrive settings (see Fig. 5).

Fig. 5. Where is the URL for Webhook SalesDrive.

This solution partially uses the functionality of integration with Bitrix24.

In particular, the exchange entity setting mechanism is used. It allows you to add/change the necessary fields in the exchange entity in user mode.

Fig. 6. Exchange Essence (Order/Pre-Order).

To work with the SalesDrive API directories for entity reference values, the ability to identify by ID has been added (this was not required (and was not) in the standard integration with Bitrix24).

Fig. 7. Directories of exchange entities with identification, incl. by ID.

Correspondences of lookup values are specified in the same way as in integration with Bitrix24.

Fig. 8. Configuring SalesDrive Reference Value Correspondences.

The object ID is stored in the same registry as for Bitrix24. To understand that this is a SalesDrive ID, it is written with the prefix "SD_":

Fig. 9. The SalesDrive ID is stored in the same register that was used in the integration with Bitrix24.

To set up the exchange entity, you can use all the fields of the request that come via Webhook (all fields of the data section in JSON Webhook SalesDrive).

Fig. 10. The principle of setting up an exchange entity for integration with SalesDrive.

The cost of standard functionality: 12000 UAH.

The cost of additional functionality:

		Price, UAH
1.	Loading additional characteristics of transactions into the BAS database (or "USP", "UVP", "UT 2.3") from СRМ "SalesDrive"	3000
2.	Unloading goods from BAS (or "UTP", "UVP", "UT 2.3") to СRМ "SalesDrive"	3000
3.	Unloading balances, cost and prices in CRM "Sales Drive"	3000

Developer: Company NCT

www.nct.ua
info@nct.ua