Skip to main content
Version: 1.7.1

Patch 1.6.4

In this version, we introduce a new table to store product achievements in the system. Another important change is that the publications can now be created automatically at the content decomposition. To achieve this, we have modified the publication and content distribution channel forms, and added states for publications.

Furthermore, we have improved the opportunity task template form. We have added new fields, configured the logic for the old and new fields. Additionally, we have deleted the crm_partner_supervisor role and replaced it with a checkbox on the customer contact form, replaced the TIN field in the customer company table with the field of the same name from the Simple application parent table, and fixed the issue of duplicate menu items in the My Work in CRM navigator section.

caution

Due to the deletion of the crm_partner_supervisor role, before the update to the 1.6.4 version, you need to install the [CRM]_1_6_4_migration.sop package and run the Migration for crm_partner_supervisor script located at the {your instance URL}/record/sys_script/174530590118661660 address. This script selects the new Show all opportunities of the partner checkbox in the contacts related to the employee accounts that have the crm_partner_supervisor role.

Read more in the documentation.

Improvements


Product achievements

We have created the new Product Achievement (crm_product_achievement) table to register the progress on the development and promotion of the company's products and services in the system.

The form, access control rules, a menu item, and states have been configured for the product achievements. The Activity Feed widget with the Additional Comments and Work Notes tabs is added to the form.

Available achievement types:

  • Certification
  • Audit
  • Rating inclusion
  • Analytical report inclusion
  • Register inclusion
  • Compliance with a standard
  • Award/Nomination
  • Regulatory compliance
  • Other

The Publications related list is located on the form. It contains the publications in which the same content item as the one in the achievement is specified.

Read more in the documentation.

Automatic generation of publications

Now, at the content decomposition, publication records may be automatically created after the creation of content tasks and packages. The publications are added for the content distribution channels that meet certain criteria. Some of the created publications' fields are completed automatically.

We have created states for publications. For this, we have added a corresponding field to the Publication (crm_publication) form and configured the URL field logic: the field becomes mandatory after changing the state to Approved and saving the record, and it remains mandatory in the Published state.

Apart from that, we have added new fields to the Content Distribution Channel (crm_content_distribution_channel) form and configured the logic for them:

FieldDescription / Logic
Is managedThe checkbox shows if the content distribution channel is under a sales direction's control.
Sales direction
  • If the Service/Product field is filled in, you can only select from the sales directions in which this service or product is specified.
  • If the Is managed checkbox is selected, the field becomes mandatory.
Service/ProductIf the Sales direction field is filled in, only the services and products related to the specified sales direction are available.
  • Content language
  • Main format
  • Target audience
If the Is managed checkbox is selected, the field becomes mandatory.

Read more:

Update of the Opportunity Task Template form

We have updated the Opportunity Task Template (crm_task_template) table form in the following ways:

  • We have added new fields:

    • Do not create task – if you select the checkbox, when a task chain is launched, the script specified in the Action field is run, but a task is not created automatically.
    • Task creation condition – in this field, you can specify a condition that needs to be met for the tasks to be created from the template when an opportunity reaches the Initiating stage. The condition can only be specified for the first task in the chain.
  • We have added the autocompletion logic for the Sort order field and for the Sales direction field. Note that the Sort order field is completed automatically only when a new template is created from the form of the previous one. The values can be changed.

  • Default value for the Time for completion in workdays field has been defined: 3.

  • We have added a reference qualifier for the Next task template field.

  • The Initiating stage and Task creation condition fields are hidden if the current template is specified as the Next task template in another record.

  • We have added the Previous Task Templates related list. It contains all templates in which the current record is specified as the Next task template.

Read more in the documentation.

Deletion of the crm_partner_supervisor role

We have deleted the crm_partner_supervisor role. Instead, we have added a new checkbox to the Customer Contact (crm_customer_contact) form: Show all opportunities of the partner. If the checkbox is selected for the contact, the employee record related to it has access to all opportunities and opportunity registrations of the partner to which the contact is related on the partner portal. If the checkbox is cleared, the contact is only able to see the opportunities and opportunity registrations that they created.

Read more:

Replacement of the B2B CRM TIN field with the similar field from the Simple application

The TIN field has been deleted from the Customer Company (crm_customer_company) table. The field of the same name from the parent Organization (org_organization) table from the Simple application has been added to the Customer Company (crm_customer_company) and Partner (crm_partner) table forms and list interfaces.

Fixes


DEF0020709: We have fixed the problem of duplicate menu items in the My Work in CRM navigator category:

  • Duplicate menu items have been renamed with the specification of the role for which the menu item is relevant. The menu items with no role specified are relevant for the primary set of roles with access to this menu item.

    Renamed menu items
    • Leads (Marketer)
    • Opportunities (Marketer)
    • Partnership Applications (Manager)
    • Partnership Agreements (Manager)
    • Marketing Campaigns (Manager)
    • Marketing Messages (Manager)
    • Content (Manager)
    • My Content Board (Manager)
  • The Content Tasks menu item is now shared by the crm_manager and crm_marketeer roles. The condition previously configured for the crm_manager role works for both roles: the table contains records of the user's sales direction for which the current user or their subordinate is specified as the Responsible.

Read more in the documentation.