Case and Pulse notification email subjects no longer contain IDs
Valid from Pega Version 7.4
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
Valid from Pega Version 7.4
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.
Improved survey authoring
Valid from Pega Version 7.4
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.
Decision logic added to surveys
Valid from Pega Version 7.4
You can now add decision logic to a survey to change the run-time order of questions. By defining a branch with conditions that skip or revisit questions, you can increase the flexibility of your survey.
For more information see Decision logic in surveys.
CRM core data types included in Pega Platform
Valid from Pega Version 7.4
Customer Relationship Management (CRM) core data types are now included with Pega® Platform, making it easier to bring your data into your Pega application. You can either import your data into the data tables for the CRM data types or use integration to communicate with your own system of record. The database tables for these data types are non-Pega formatted, which gives you better performance and more control over your data.
For information about the database tables, see CRM data types in Pega Platform.
Support for extracting data from file attachments during email triage
Valid from Pega Version 7.4
With the Pega® Intelligent Virtual Assistant for Email, when you triage email interaction cases, the system can now use defined text analyzers to detect entities in files that are attached to the received email. The following file types are supported: DOC, DOCX, ODT, PDF, RTF, and TXT. This feature improves the machine learning and case processing capability for the Email user channel.
For more information, see Enabling the analysis of attached files during email triage.
Support for multiple attachments added to Pulse
Valid from Pega Version 7.4
You can now upload more than one attachment to posts and comments in Pulse. Because Pulse maintains the continuity of attachments in posts, email messages, and email notifications, you can use it to quickly follow conversations in a case.
For more information about the features that Pulse supports, see Communicating with Pulse.
Manage propositions in multitenant environments
Valid from Pega Version 7.4
Proposition Management is now supported in multitenant environments of Pega® Platform. The DisablePropCache Dynamic System Setting switches off the use of a proposition cache. When you import propositions in strategies, you can import only versioned propositions (Decision Data rules). Unversioned propositions are not supported under this setting, but these can be converted to versioned propositions.
For more information, see Unversioned propositions, Synchronization of the proposition cache, and Converting groups with unversioned propositions.
VTable dispatch mechanism for HTML control execution improves performance
Valid from Pega Version 7.4
Pega® Platform now uses an optimized VTable dispatch mechanism to manage rule execution for the Text Input and Formatted Text Input controls. This change improves performance by eliminating the dependency between stream rules and HTML controls during rule assembly. Disabling this feature will have a negative effect on performance and is not recommended. However, you can disable this feature by adding the following configuration parameter:
Name: assembly/section/control/vtable
Value: false
Layout groups and design templates
Valid from Pega Version 7.4
On the Design tab of the Section form in Designer Studio, you can use a layout group to display closely related information by using accordion, menu, stacked, or tab navigation elements. You can then create a templated region that is based on the layout group. For example, you can use this type of region to enable users to add, reorder, or remove tabs from screens at run time in Pega® Express.
For more information, see Creating a templated region based on a layout group and Creating a templated region based on a layout group.