Version 1.4.1
New features
In this version we added the functionality of content decomposition (creating child content tasks and packages automatically), improved the table forms that relate to content development, and added the rules for the default completion and limitations to the values of certain fields. These changes help facilitate content development.
Content decomposition
A new Decompose button that opens the Decompose content modal window has been added to the content form. There, you can select all formats, languages and target audiences for which the content needs to be adapted. The content tasks and packages are created automatically for all intersections of the selected values. This functionality streamlines the content development, allowing to plan the whole process in advance and avoid manual creation of child tasks.
Some of the fields are completed by default for the created records:
Field values of the Content tasks created by decomposition
| Field | Value |
|---|---|
| Subject | The subject is generated automatically according to the following template: [Content format] Content name. |
| Content format | One of the formats specified at the decomposition. |
| State | Backlog |
| Content | The content for which the task is created. |
| Responsible | The employee who decomposed the content. |
Field values of the Content packages created by decomposition
| Field | Value |
|---|---|
| Name | The name is generated automatically according to the following template: [Content format, Content language, Target audience] Content name. |
| Content language | One of the languages specified at the decomposition. |
| Target audience | One of the target audiences specified at the decomposition. |
| State | Thematic pool |
| Content task | One of the content tasks created at the decomposition. |
Improved forms of Content Management section
New fields have been added to the following forms:
- Marketing Messages. Two tabs have also been added to the form: General and Notes.
- Content
- Content Taks
- Publications
Some of the new fields have been added to the form through Dot-walking for the employees responsible for the child records to see crucial information of the parent records without opening them. For instance, an employee responsible for the content task can see on its form the service or product to which the marketing message, on which the parent content is based, is related. These fields are read-only.
Apart from that, a new Marketing Messages related list has been added to the Pain form.
The current structure of the forms mentioned above is described in the documentation.
Logic for filling in the fields and automatic state transitions
The following rules for automatic state transitions have been added:
| Record | Rule to change the state to Published | Rule to change the state to Canceled |
|---|---|---|
| Content | All related content tasks become Published or Canceled. | All related content tasks become Canceled. |
| Content task | All related content packages become Published or Canceled. | All related content packages become Canceled. |
The Content Management section forms now have the rules for specifying available value ranges for the new and old fields and adding default values for some of them.
- Marketing Messages
- Content
- Content Tasks
| Field | Rule |
|---|---|
| Pain | If the Service/Product field is completed, it is only possible to select the pain related to the specified record. The field becomes mandatory if the value of the Recognition ladder step field equals to 1. Awareness of the problem and a possible solution. |
| Communication objective | If the Recognition ladder step field is completed, it is only possible to select the communication objective related to the specified record. |
| Differentiator | If the Service/Product field is completed, it is only possible to select the dfferentiator related to the specified record. The field becomes mandatory if the value of the Recognition ladder step field equals 3. Selection of supplier. |
| Recognition ladder transition problem | If the Service/Product or Recognition ladder step field is completed, it is only possible to select the problem related to the specified record. The field becomes mandatory if the value of the Recognition ladder step field is not equal to 1. Awareness of the problem and a possible solution or 3. Selection of supplier. |
| Sales direction | By default, the field is filled in with one of the sales directions to which the user that creates the record belongs to. If the user is not related to any sales direction, the default sales direction specified in the crm.selling_direction.default system property is used instead. If the Service/Product field is completed, it is only possible to select the direction related to the specified record. |
| Service/Product | If the Sales direction field is completed, it is only possible to select the service or product related to the specified record. |
| Field | Rule |
|---|---|
| Author | By default, the employee that creates the record is added to this field. |
| Field | Rule |
|---|---|
| Subject | By default, the field is filled in with the name of the selected Content. |
| Verifier | By default, the field is filled in with the employee selected as the Subject-matter expert for the related Content. |
| Content structure | By default, the field is filled in with the value of the same-name field from the selected Content. |
| Responsible | By default, the employee that creates the record is added to this field. |
Fixes
DEF0018341: The Sales direction term is now used everywhere in the application instead of Selling direction, the texts have been fixed.
DEF0019198: A fix for the error that did not allow the CRM Tasks with Other related element type to be edited by the record creator. We added access control rules that enable record creators to edit the records for the following roles:
- crm_manager
- сrm_sales
- crm_marketeer
DEF0019322: The contact phone number specified at the qualification was not saved if it contained the + sign. Now, the contact phone number is saved, and contains only digits. All other characters are deleted from the value while record saving and qualification.
DEF0019428: The sorting has been added to the Opportunity Stages table list interface. The opportunity stages are now filtered in the ascending order by default.