Skip to main content
Version: 1.7.1

Version 1.7.0

In the new version we have significantly extended the certification functionality. Now, you can:

  • create certification stages and configure their order;
  • specify the certification programs that need to be completed by the partner company employees to obtain a partner level, and connect the relevant certificates to partnership agreements;
  • create certificates for internal company employees.

Apart from the changes related to the certification programs, we have improved the process of company merging, and fixed the issues related to the work of the CRM SharePoint create folder widget and the application's kanban boards.

New features​

Certification stages​

It is now possible to create certification stages and issue certificates for their completion. For this, we have added the Certification Stage (crm_certification_stage) table inherited from the Certification (crm_dev_certificates) table. On the stage form, you can specify the parent certification program and the order of this stage compared to the other stages of this certification. The list of existing stages and the creation of a new one are available in the new Certification Stages menu item.

Additionally, the new Certification Stages related list has been added to the Certification form. There, you can see all stages of the current certification and create a new one.

Read more in the documentation.

Certificates for partnership agreements​

We have added a new field called Certifications to the Partner Level (crm_partner_level) table form. In this field, you can specify the programs that the partner company employees need to complete for the company to meet the criteria of this level. Apart from that, we have extended the logic of the Partnership program field on the Partnership agreement (crm_partnership_agreement) form: if Certifications are specified in the selected Partner level, you can only specify a partnership program that has the same Vendor as the certifications specified in the partner level.

We have also created a new M2M table called Certificates for Partnership Agreement (crm_certificates_for_partnership_agreement) in which you can establish a connection between a partnership agreement and a certificate of a partner company employee relevant for this agreement. These can be the certificates that the partner company employees received to meet the requirements of the requested partner level in the current program, or the certificates that the partner company employees had prior to the conclusion of the agreement but that are relevant for it.

Such a connection can be added through a new related list of the Partnership Agreement (crm_partnership_agreement) form called Certificates. The New and Delete UI actions are available in this related list for you to control such connections.

Read more in the documentation.

Certificates for internal company employees​

We have implemented the ability to create certificates for employees of the Internal class companies. To achieve this, we have added new fields to the Certificate (crm_contact_certificate) form: Is an internal employee and Employee. When the Is an internal employee checkbox is selected, the Specialist contact field gets hidden, and the Employee field appears. In this field, you can specify an employee of the Internal class company. When an employee is specified in this field, the Company field is completed automatically with their company.

The employees to whom certificates are issued receive notifications about the certificate expiration dates, the same as the contacts related to the certificates.

Read more in the documentation.

Improvements​

Company merging improvements​
  • Now, at the merging of companies all types of actions created for the duplicate companies are connected to the main company. These actions are recorded into the Actions field of the Duplicate Companies Log (crm_company_merge_log) form that was previously called Tasks. The title of the field was changed to correspond to its extended content.
  • If the Name, TIN, or Website field is not completed in the duplicate company, this field is completed with the value from the main company when merged.
  • The main company's Name, TIN, and Website fields must be completed for the duplicates to be merged with it.
  • Now, the mandatory markers of some of the application tables' form fields are configured through a client script instead of the column attribute. This helps avoid errors when the records of these tables are connected to the main company at the merging. The list of such forms:
    • Customer Contact (crm_customer_contact)
    • Opportunity (crm_opportunity)
    • Certificate (crm_contact_certificate). The read-only attribute of the Serial number column of the certificates is now also implemented through the script.
    • Marketing List (crm_marketing_list)
    • Action (crm_action) and its child tables' forms.

Read more in the documentation.

Fixes​

DEF0021361: The CRM SharePoint create folder widget was displayed on the forms of the creation of the Content (crm_content), Opportunity (crm_opportunity), and Customer Company (crm_customer_company) table records. Now, the widget is only displayed on the forms of saved records.

DEF0021161: We have fixed a set of defects related to the work of the application's kanban boards:

  • The exclusion of states did not work: they continued to be displayed on the board despite being specified in the Excluded states field (the excluded_states JSON parameter). It has been fixed, and the excluded states are no longer displayed on the board.
  • When a blocked board card was opened in a new tab, error toasts were displayed on the board tab. Now, no errors appear in this case.
  • It was impossible to open a card that had no title specified because only the title contained the link to the record. The issue has been fixed: now, clicking anywhere in the card area opens the record in the new tab.