Published Release Notes

Support for NLP model training in the Facebook and WebChat user channels

You can now train and enhance the natural language processing (NLP) model in a Facebook or WebChat user channel to support machine learning. You can review user statements and questions, edit the text, and map content to specific text analyzer categories.

For more information, see NLP model for a Facebook channel and NLP model for a WebChat channel.

Label changes for text analytic models

The classification analysis label has changed to topic detection and the entity extraction label has changed to text extraction. Also, the sentiment analysis, topic detection, and intent detection labels are now located under Text Categorization in the Analytics Center. These name changes reflect industry standards and provide a clearer distinction between different types of text analytics models in Pega^® Platform.

For more information, see Text analytics models.

Automatically detect the most important themes in text

Text analyzers can now automatically recognize the most important concepts that are expressed in text and mark such concepts as entities of type auto_tags. You can use auto_tags to group similar content by its themes and reduce the dimensionality of text to the most important features.

For more information, see Text extraction analysis.

Data pages can source information from a robotic process automation

When you use robotic process automation (RPA), you can now configure data pages to source information from robotic automations so that you can connect your Pega® Platform application to legacy applications in your enterprise. By using automations to retrieve data and save it to a data page, you can use data virtualization to encapsulate your Pega Platform data model from the physical interface of a legacy system against which the automation is running.

For more information, see Obtaining information from robotic automations.

Case and Pulse notification email subjects no longer contain IDs

The subjects of notification emails for cases no longer contain case IDs, and for Pulse, they no longer contain Pulse message IDs. The system now interacts with email clients by using the information that is stored in the email headers. As a result, comments are posted on a conversation even if users edit the subjects when they reply to these emails. Because the system also sends the replies as emails to the relevant users in the conversation, editing the subjects allows users to give appropriate descriptions of the emails to the relevant users.

For more information about email notifications, see:

• Pega^® Express 7.4 – Communicating with Pulse
• Pega Platform 7.4 – Communicating with Pulse

Legacy rules removed to reduce Pega Platform installation size

The installation of Pega^® Platform 7.4 removes deprecated and unused rules. The smaller installation size decreases rule sync time and reduces the amount of storage required for Pega Platform. In addition, the smaller installation reduces the rule database size and shortens installation and upgrade times. You can access the legacy rules, if needed, in the PegaLegacyRules:01-01-01 in the Resource Kit on the Pega Platform media.

For more information see Finding legacy rules in sections.

Survey rules are deprecated

Surveys that were created prior to version 7.4 of Pega Platform are now deprecated. As a best practice, recreate your survey by using the Survey Management landing page, and then reuse questions or question pages from your survey library.

For more information about creating surveys, see Improved survey authoring.

Questionnaire shape replaces Survey shape in legacy flows

In flows that reference deprecated surveys, the Questionnaire shape has replaced the Survey shape. Although legacy surveys continue to function in this release, update your flows to use the Survey shape because it provides the latest survey capabilities, and deprecated features are not supported.

For more information about the new survey authoring experience, see Improved survey authoring.

Limited question and answer formats in new surveys

Complex questions and some answer formats for simple questions, such as attachment, are not supported by the new surveys that you create. Although you can create stand-alone questions in your survey library that use these formats, you can add these questions to legacy surveys only.

For more information about supported answer formats, see Answer formats for questions in a survey.

Improved survey authoring

You can now add functionality, such as validation and visibility conditions, to a survey without having to manage multiple rule forms. By using the centralized options on the Survey Management landing page, you can visualize changes to survey items in real time and configure surveys more quickly.

For more information about improved options, see Streamlined survey configuration.