Version 1.6.0
In the new version, we have added the ability of integrating external services, receiving data through these integrations and using it in the system. The "out-of-the-box" B2B CRM application now includes an integration with the DaData service, through which the system can receive a company's legal name by its TIN.
Another important feature is the visual editor of the B2B CRM kanban boards. We have completely redesigned the kanban board form. Now, the administrator can configure the boards on the form directly in its fields instead of configuring a JSON structure. It has also became possible to create the boards manually for the required tables.
Additionally, we have upgraded access restrictions to customer company records for the partner representatives on the portal. We have added new fields for publications and an automatic state transition for a content package when a related publication is created. Besides, we have fixed an issue that did not allow to create a contract for a won opportunity from its form.
New features
Integrations with external systems for acquiring data
We have designed the functionality required for the integration of external systems with the B2B CRM application to acquire the data from them and use that data in the application. The use of integrations increases the reliability of the data stored in the application tables and automates a part of the data collection process.
For this, we have created three new tables:
- CRM Integration (crm_integration) – a table with integration records. The integration records contain the information required for the SimpleOne system to connect to an external system, and an integration script.
- Integration Parameter (crm_integration_parameter) – a table with records of the parameters in which the data received through integrations is saved.
- Mapping (crm_mapping) – a table that contains directions for the system to associate external API properties with the corresponding parameters in the SimpleOne system.
After the configuration of the integration, you can use the data received through it by calling a new CRMIntegrationHandler handler in scripts.
Detailed information about the integrations is available in the documentation.
DaData integration
With the new functionality, we have integrated the DaData service for receiving company legal names by TIN. Now, if the DaData integration is active on your instance, the new Full name field of the Customer Company (crm_customer_company) form is automatically completed with the company's legal name received from the external service after you specify the TIN on the customer company form.
The integration is available by default but you need to activate it. Detailed information about the integration and its activation is available in the documentation.
Kanban board visual editor
We have completely redesigned the form and configuration of kanban boards of the B2B CRM application. We have added new sections and fields to the Sales Direction Board (crm_selling_direction_board) form for the administrators to configure any board of the application through a convenient and user-friendly interface:
- General – the section contains general kanban board settings, such as the choice of the table, the records of which need to be displayed on the board, and the background image.
- Cards – the section contains the board card settings: the choice of the columns from the specified table for their values to be displayed on the cards, the configuration of blocking condition for the cards, and the configuration of badges.
- Swimlanes – the section contains all settings of the board swimlanes and columns: swimlane names, the configuration of the expedite swimlane, the states displayed on the board, the areas, and the WIP limits.
The new fields visualize the settings that previously could only be configured through a JSON structure.
Additionally, we have added manual creation of the boards: now, you can create a kanban board for any table of the B2B CRM application if it has at least one column of type Choice and Reference: employee.
We have also kept the previously available way of configuration: on the board form, click Configure JSON to open a modal window where you can configure a JSON structure.
Detailed information about improved board editor is available in the documentation.
Improvements
Access restrictions for partners to the company records on the portal
We have limited access to the customer company records on the partner portal for partners (users with the crm_partner_supervisor role or no role). Now, the dictionaries contain only active records of the Customer Company (crm_customer_company) table with the Customer class, and the company to which the partner representative belongs.
Additionally, when a company is added via a partner portal by a user with the crm_partner_supervisor role or no role, the system validates the uniqueness of the Company name, Company website, and Company TIN fields only among the companies to which the current user has access.
Publication improvements
We have added new fields to the Publication (crm_publication) table form. These fields are hidden by default and read-only. You can add them to the form or use for filtering.
All of these fields are completed automatically with the values from the content entities of higher levels (content package, content task, content, marketing message) if the corresponding fields are completed in them. If the content package is not specified for a publication, none of the fields listed below is completed.
Field list
| Field | Description |
|---|---|
| Content language | The language of the published content package. |
| Target audience | The target audience of the published content package. |
| Content task | The content task from which the published content package was created. |
| Content format | The format of the content task from which the published content package was created. |
| Content | The content from which the content task was created. |
| Marketing message | The marketing message of the content. |
| Service/Product | The service or product promoted in the marketing message. |
| Pain | The customer pain at which the marketing message is aimed. |
| Differentiator | The differentiator highlighted by the marketing message. |
| Recognition ladder transition problem | The recognition ladder transition problem which the marketing message aims to solve. |
| Communication objective | The communication objective of the marketing message. |
| Recognition ladder step | The recognition ladder step to which the marketing message is dedicated. |
| Sales direction | The sales direction of the marketing message. |
Additionally, now a content package automatically transitions into the Published state when a publication is added for it.
Read more in the documentation.
Fixes
DEF0020832: It was not possible to create a contract for a won opportunity from its form: an error about a mandatory field not being completed appeared. The issue is fixed, the field completion is validated correctly, and the contract can again be created from the opportunity form.