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.

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.

Enhanced adaptive model reporting

The new Model report replaces the Behavior and the Performance overview reports to improve report usability and provide consistent information. You can export your Model reports into PDF or Excel files to view or share them outside the Pega® Platform. The Model report also includes information on the groups of correlated predictors where the best performing predictor from each group is active in the model and other remain inactive; this information helps you understand why predictors are active or inactive.

For more information, see Generating a model report.

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.

Use Kinesis data sets in Pega Decision Management

You can create Kinesis data set instances to connect to Amazon Kinesis Data Streams and use this data set in decision management for processing real-time streaming data. Integrating Kinesis data streams into Pega® Platform in the cloud provides a fault-tolerant and scalable solution for processing IT infrastructure log data, application logs, social media, market data feeds, and web clickstream data.

For more information, see Creating a Kinesis data set.

Store and scale the processing of Stream data records on multiple nodes

You can configure the Stream service on Pega^® Platform to ingest, route, and deliver high volumes of low-latency data such as web clicks, transactions, sensor data, and customer interaction history. You can store streams of records in a fault-tolerant way and process stream records as they occur. Add or remove Stream nodes to increase or decrease the use of the Stream service and optimize data processing.

For more information, see Stream service overview.

Decisioning services now use default node classification

Decisioning services have been integrated with default node classification on Pega^® Platform to provide a unified way of creating and initializing services. As a result of the integration, the Data Flow service has been divided into Batch and Real Time services to better handle different types of data flow runs. You can now specify separate subsets of Data Flow nodes for batch data flow runs and real-time data flow runs to divide the workload between these two subsets.

For more information, see Node classification, Data Flows landing page, and Services landing page.

Train machine learning models for extracting named entities and detecting intents

Data scientists can train machine learning-based text extraction and intent detection models by using the Analytics Center. With text extraction, you can train a Conditional Random Fields (CRF) model to detect whether the content contains specified entity types such as person names, company and organization names, locations, dates and times, percentages, and monetary amounts. For intent detection, you can train a maximum entropy model to understand user intentions expressed in written content. With these two new capabilities, you can quickly react to customer queries and comments by taking appropriate action against the information that you extracted.

For more information, see Creating machine learning-based text extraction models and Creating machine learning-based intent analysis models.

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.