Skip to main content
Version: 1.9.0

B2B CRM Application Deployment

To deploy the B2B CRM application, complete the following steps:

  1. Install the B2B CRM application.
  2. (optional) Deploy the demodata.

To install the B2B CRM application for the first time, use the full version pack. To update the application from the previous versions, use the update packages.

caution

Note that different B2B CRM versions are compatible with different platform versions. If required, update the platform version, otherwise the B2B CRM application will not work correctly.

Deploy full version​

tip

Role required: admin.

To install the B2B CRM application to your instance from scratch, complete the following steps:

Required platform version

B2B CRM versionCompatible platform versions
1.2.1, 1.2.2, 1.3.0, 1.3.1, 1.3.21.18.1 – 1.22.3 (inclusively)
1.4.0, 1.4.1, 1.5.0, 1.5.1, 1.5.21.18.1 – 1.23.3 (inclusively)
1.5.3, 1.5.41.24.2 and above
1.5.5, 1.6.01.25.0 and above
1.6.2, 1.6.31.28.0
1.6.4, 1.7.0, 1.7.1, 1.8.0, 1.9.01.28.2 and above

Starting from the 1.2.1 version, the master data and demo data are included in separate files.

  1. Install the [CRM]_1_2_1_full.sop package.
  2. Import the JSON file with the master data [CRM]_1_2_1_master_data.json.
  3. (optional) Import the JSON file with the demo data [CRM]_1_2_1_demo_data.json.
  4. (optional) Install the package with the demo data [CRM]_1_2_1_demo_data.sop.

The numbers in the file titles may be different from the ones mentioned in the instruction depending on the installed version.

Install updates​

tip

Role required: admin.

Install all versions and patches in their release order.

Example:

To update the application from version 1.1.0 to 1.5.5, sequentially install the update packages in the following order: 1.2.0, 1.2.1, 1.2.2, 1.3.0, 1.3.1 and so on until 1.5.5. Always follow the version deployment instructions.

Demonstration data features:

  • the demo data pack installed remains on your instance even after the application update.
  • install new demo data packs over the existing demo records. The records will be updated.

Update version 1.8.0 to version 1.9.0​

Required platform version: 1.28.2 and above.

  1. Install the [CRM]_1_9_0.sop package.
  2. Navigate to System Settings → Server Scripts and open the Change partner to agreement in lead script located at the {your instance URL}/record/sys_script/176493369113213667 address and click Run. The script completes the Partnership application field on the forms of Leads (crm_leads) in the New, Assigned, and Qualified states if Partner is specified, according to the following logic:
  3. If the partner company has only one partnership agreement, it is used as the value.
  4. If the partner company has more than one partnership agreement, the system selects the agreement whose Partnership program includes the Service/Product specified in the lead.
  5. If there is more than one such agreement, an agreement for the Partner level with higher Level weight is selected.
  6. If there is more than one such agreement for levels with identical weight, the latest created agreement is selected.

If the script fails to complete the Partnership application field in some records, you will see a toast message with their list.

  1. (optional) If you use the DaData integration, navigate to System Settings → Server Scripts. Open the forms of the server scripts described below and Run them in the same order as in the table:

    OrderNameRecord IDDescription
    1Update customer companies by TIN175948892401699909The script finds records of the Customer Company (crm_customer_company) table with the completed TIN field. A DaData request is triggered for each such record. After that, empty fields of the External Data tab on the Customer Company form are completed with the data received if they are present in the DaData.
    2Update customer company if inn is empty175930707205723828The script finds records of the Customer Company (crm_customer_company) table with the empty TIN field. If the Main contact is specified for a record, the Email of this contact is used for search in DaData. If the main contact is not specified or has no email specified, the emails of other contacts in which the current company is specified are used for search.
    • If a company with such an email is found, its TIN is specified on the company form on your instance, and the script moves to the next company.
    • If no company with such an email is found, the script proceeds to check the email address of the next contact in which this company is specified. It continues until a match is found in DaData or all the contacts are checked.
    3Update customer contact if empty company175947498701784863The script finds records of the Customer Contact (crm_customer_contact) table with the empty Company field. For each such record, a request to DaData is sent using their Email. If a company with matching email is found, and there is a record in the Customer Company (crm_customer_company) table or its child table on your instance that has the same TIN as the company found by the script, the Company field of the contact is completed with this record. If such a company is not found in DaData or on your instance, the contact remains unchanged.

  2. (optional) If you use the Ainergy integration for adding widgets to the Lead (crm_leads) form, open the server script record Add Ain Call and Smart Filling to Leads located at the {your instance URL}/record/sys_script/175429644308553855 address and click Run. This script adds Ainergy widgets to the Lead form.

  3. (optional) If you use the Ainergy integration for content generation, install the [CRM]_CRM_1_9_0_AIN_1_12_0.sop package with the prompts required for the work of the integration.