Skip to main content
Version: 1.6.3

Patch 1.6.3

We have created a widget for the displaying of text with the Markdown formatting applied on the form. We have also improved the processes of content development and opportunity processing, added a checkbox to specify if a new contact added from the lead form wants to receive emails, and fixed the problem of accounts created from the contact form having weak passwords.

New features​

View Markdown-formatted text on the content and its child entities' forms​

We have developed a new widget, CRM MD Beautifier. It can display Markdown-formatted information added to a text field.

The widget consists of a text input field and a text preview field:

The list of elements supported by the widget:

  • Headlines up to the sixth level (inclusively).
  • Images. Note that the images inserted in the text are scaled if they exceed the maximum allowed width for your screen resolution.
  • Links. The users can click the links to open the specified resource in the current tab.
  • Bulleted lists.
  • Numbered lists.
  • Bold text.
  • Italic text.
  • Underlined text.
  • Strikethrough text.
  • Code.
  • Quotes.

The Markdown text field has been added to the Content (crm_content), Content Task (crm_content_task), and Content Package (crm_content_package) forms. The new widget is attached to these fields, so now you can save the text of future publications in the system with the ability of previewing them.

Read more in the documentation.

Improvements​

Content improvements​

We have made a set of improvements to the content module:

  • The Related content field has been added to the Content form, and the Publication date field has been hidden from it.

  • The logic of automatic search for a matching content distribution channel has been added to the URL field of the Publication form. When you complete this field, the system checks if there is a content distribution channel with the same address. If such a record is not found, the search is repeated with a value shortened to the first / sign. If a matching record is found, the Content distribution channel field is automatically filled in with it.

  • At the content decomposition, the created content tasks now automatically enter the Thematic pool state instead of Backlog.

  • The Cancel unpublished UI-action has been added to the Content and Content Task forms. When used, the child content tasks (for content) and content packages (for content tasks) move into the Canceled state if they have not been Published yet. If the record on the form of which the action is performed (a content or content task record) has not been Published, it becomes Canceled.

  • When a content record moves into the Canceled state, the related content tasks that have not been Published become Canceled.

  • When a content task moves into the Canceled state, the related content packages that have not been Published become Canceled.

  • The Sales direction field has been added to the Tag (crm_tag), Pain (crm_pain), Differentiator (crm_differentiator), and Recognition Ladder Transition Problem (crm_transition_problem) forms, and the following logic has been configured for it:

    • The field is automatically completed with the first found sales direction of the current user. If the user belongs to more than one sales direction, you can change the value to any of them.
    • If the Service/Product field is completed, an additional limitation is applied to this field's value: the sales direction must be related to the specified service or product.

    Similar logic has been added to the Service/Product field:

    • You can only specify a service or product related to the sales directions of the current user.
    • If the Sales direction field is completed, only the services and products of this direction can be specified.

    Finally, we have changed the access control rules for the tables mentioned in this paragraph: now, users with the crm_sales, crm_manager, crm_marketeer, crm_pam, crm_certificate_manager roles can edit and delete records related only to their sales directions.

Read more in the documentation:

A checkbox to block sending emails on the Lead form​

We have added the Do not send emails checkbox to the Lead (crm_lead) form, so now when a new contact is added from the lead form, you can specify if the contact does not want to receive emails.

Improvements to the processing of partner opportunities​

The Link DRD Draft field is now non-mandatory in all opportunity stages. Additionally, we have added a reference qualifier to the Key regions field of the partnership agreements, therefore the countries added to the system are now displayed in its dictionary by default.

Fixes​

DEF0021237: Previously, strong password requirements were not applied to the employee accounts created from the Customer Contact form with the Create account UI-action. Now, the password of employee accounts created by this method must contain at least eight symbols, including letters in both lower and upper cases, and digits.