Published Release Notes

Extract data from Pega Cloud to an on-premises database

You can now use Pega^® Business Intelligence Exchange (BIX) to extract data from Pega Cloud to an on-premises relational database management system. Extracting data from Pega Cloud directly to an on-premises database improves efficiency by eliminating the need for file extraction and the development of a file extraction infrastructure.

For more information, see Extracting data from Pega Cloud to an on-premises database.

Improved connection pooling performance

HikariCP is now used for connection pooling for databases that are configured by using a URL. HikariCP improves connection pooling performance; however, more database connections might be used than in previous versions of Pega^® Platform.

As a result of the switch to HikariCP, you cannot use the System Management Application (SMA) to get diagnostic data from your application. For instructions about how to get diagnostic data by using REST services, see Obtaining connection pool diagnostic data by using REST services.

Stakeholder management extended to case followers

You can now control which users follow a case. By actively involving the people with relevant skills and roles in your application, you can resolve cases more quickly.

For more information, see Case followers.

No longer supported translator configuration options

The following translator configuration options are not needed and are no longer supported. If you previously configured any of these system settings, remove them from the system settings to avoid a warning message. For example, if you set translator/useparserfamily, the following message is displayed at startup: "Translator option, 'translator/useparserfamily' is not needed and no longer supported. Remove this from the system settings."

• translator/useparserfamily
• translator/usecodegenerator
• translator/usenativedouble
• translator/optimization/use71BlockAnalysis
• translator/optimization/use71ConstantFolding
• translator/optimization/use71AssignmentTypeSimplification
• translator/optimization/use71IntrinsicFunctions
• translator/use71PropSetGeneration
• translator/use71ParserAssignment
• assembly/model/useBlock4ContiguousSets
• /translator/pandc/comparepandcalgorithms
• /translator/pandc/use6xalgorithms
• /Compatibility/CheckForTopLevelClassMismatch

In addition, the com.pega.pegarules.generation.parseoverride bootstrap option is no longer supported. Remove this option from the system settings.

System state data is saved for 90 days

System state data is now saved to the database for 90 days and can be downloaded as a JSON file. Having previous system state data available is useful for debugging system problems. Operators with the pzSystemOperationsObserver privilege can download system state data from the Cluster Management landing page for either the entire cluster or a single node. In addition, the PersistClusterState and PersistNodeState agents have been added to the Pega-RulesEngine ruleset for persisting system state data to the database.

For more information, see Downloading the system state.

Pulse enhancements

The enhanced layout of the Pulse interface provides a better user experience for posting messages, adding attachments, bookmarking content, and so on. You can now post messages in your activity feed, format messages, add inline images and links to messages, reference cases, and view the list of users who like messages. The Pulse email templates have also been improved to display email content in a coherent and structured format.

For more information, see:

• Pega Express 7.4 – Communicating with Pulse
• Pega Platform 7.4 – Pulse enhancements for social collaboration

View attachments inline

You can now view thumbnails of PDF file and image attachments and icons of video attachments in Pulse, cases, and other areas of the application that allow you to attach files. Thumbnails provide a preview of your attachments inline. You can also play video attachments and expand the thumbnails of PDF file and image attachments to view them in readable formats.

For more information, see Inline preview of attachments.

Edit icons and titles for messages in the activity feed

You can now edit the icons and titles of messages that are displayed in the activity feed for Pulse by customizing the pxFeed Pulse gadget. For example, to inform other users of an application about important Twitter updates that are related to the organization, you can create a message that displays a Twitter icon and a title of Twitter updates.

For more information, see Pulse enhancements for social collaboration.

Activity feed displays application messages

The activity feed for Pulse now displays messages within the context of the application of the logged-in user. If a user posts messages within the context of the application, all the users of the application can view the messages in their activity feed. Users can select the filter for application messages to view only these messages. For example, application messages can be used for release announcements.

For more information, see:

• Pega^® Express 7.4 – Communicating with Pulse
• Pega Platform 7.4 – Pulse enhancements for social collaboration

pxFeed replaces pxContextFeed and pxActivityFeed Pulse gadgets

The pxContextFeed and pxActivityFeed gadgets have been replaced by the pxFeed gadget to integrate the functionalities of viewing and posting messages in the Pulse activity feed. You can include this gadget within a section or harness across your application, for example, in the dashboard of the Case Manager portal, to display the activity feed. You must add the latest UI Kit ruleset to ensure that your application uses the pxFeed gadget instead of the pxContextFeed and pxActivityFeed gadgets to generate the activity feed.

For more information, see Pulse gadget and custom APIs.