Published Release Notes

Ability to include all properties in search results

You can now include all properties in a class in search results so that they can be used in report filtering. When the Enable search results for all properties option is selected on the Custom Search Properties rule form, all top level and embedded page scalar properties for the class are indexed and returned in search results, and all embedded page list, page group, value list, and value group properties for the class are indexed but not returned in search results. Selecting this option might affect performance.

In addition, by default, properties defined in the Data-Tag-RelevantRecord instance for a class are indexed and returned in search results and do not need to be explicitly configured.

You must reindex search after selecting or clearing Enable search results for all properties and after changing the properties that are defined in the Data-Tag-RelevantRecord instance.

For more information, see Specifying custom search properties.

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.

Compact style sheet for creating PDF files

You can now use a compact style sheet when you create PDF files by using the Create PDF smart shape in a case type or when you use the HTMLtoPDF activity. This style sheet overrides the style sheet that is used by the harness skin and correctly renders certain elements such as headings and inline grid tables. It also renders PDF files more quickly.

For more information, see Creating PDF files by using a compact style sheet and PDF file rendering scenarios.

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.