Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Trace agents from the Agent Management landing page

Valid from Pega Version 7.2.2

You can now trace an agent on any node in the cluster from the Agent Management landing page without logging in to the individual nodes. From this landing page, you also specify when to trace an agent.

For more information, see Tracing agents.

New graphical layout and shapes on the Data Flow form

Valid from Pega Version 7.2.2

The Data Flow form has an enhanced layout that improves interaction with objects on the canvas and provides better readability of flow shapes. The enhancements also include the addition of Branch and Data Transform shapes, and the Convert shape, which supports page unpacking. With these enhancements, you can build data flows more efficiently and capture business requirements more effectively.

For more information, see Improvements to the Data Flow rule form and New shapes on the Data Flow form.

Client page load statistic enhancements

Valid from Pega Version 7.2.2

The client page load statistic is the total elapsed time from when the user clicks to when the screen has finished rendering, including network time and time spent in the browser. This statistic gives you visibility into system performance, allowing you to address performance issues in a timely manner. The client page load statistic is now available for usage reporting through the Log-Usage class and in the System Management Application (SMA). In addition, a new alert, PEGA0069, is generated when the page load duration is greater than the threshold. The threshold is set by using the following prconfig.xml file setting:

<env name="alerts/browser/clientPageLoadTimeThreshold/warnMS" value="<milliseconds>" />

The default is 4000 milliseconds.

For more information, see PEGA0069 alert - Client page load time has exceed the alert threshold.

Monte Carlo data set

Valid from Pega Version 7.2.2

You can now create a Monte Carlo data set that is filled with varied and realistic-looking data. You can use this type of data set to generate random data records to test strategies and data flows.

For more information, see Creating a Monte Carlo data set record.

Deploy revisions directly in target environments

Valid from Pega Version 7.3

As a revision manager, you can now directly deploy or migrate completed revisions to multiple Pega 7 Platform environments that were configured as targets by the system architect. The revision management process is faster because you do not need to package a revision as a JAR file, and then manually import that file to the Pega 7 Platform. Additionally, this solution gives business users more control over application rulesets and enables them to act more independently.

For more information, see Direct deployment of revisions.

System starts slowly after upgrade or update on IBM DB2 for z/OS

Valid from Pega Version 7.2.2

Additional tables are added to upgraded and updated systems. If your system starts up very slowly after an upgrade or update, the database statistics on these new tables might not have generated correctly. To correct this issue and improve performance, your database administrator needs to manually rebuild the statistics for all tables in the rules schema.

The UpdateAdaptiveModels agent causes an exception after Pega 7.2 to 7.2.1 upgrade

Valid from Pega Version 7.2.1

After the Pega 7 Platform is upgraded from version 7.2 to 7.2.1, the log files might show an error that is caused by the UpdateAdaptiveModels agent. This agent is enabled by default and is responsible for updating scoring models in the Pega 7 Platform. If you use adaptive models in your solution, you can avoid this error by configuring the Adaptive Decision Manager service. If you do not use adaptive models, disable the UpdateAdaptiveModels agent.

For more information, see Configuring the Adaptive Decision Manager service and Pega-DecisionEngine agents.

Support for creating PegaUnit test cases for strategy rules

Valid from Pega Version 7.2.2

You can create PegaUnit test cases for strategy rules in Designer Studio and in the decisioning user portals to compare the output of a strategy to the results that are returned by running the strategy. For example, you can verify that the number of propositions per customer is less than or equal to a certain value.

For more information, see:

Simplified support for external log management systems

Valid from Pega Version 7.2.2

Simplified support for external log management systems such as ELK (Elasticsearch, Logstash, Kibana) makes it easier to implement an external log management system. An external log management system can improve access to system log files that help diagnose and debug issues by eliminating the need to download log files from each node in the cluster.

For information about configuring ELK, see Configuring ELK for log management.

For information about using Kibana to view log files, see Pega logs in Kibana.

Export and import operations for data sets

Valid from Pega Version 7.2.2

You can move data between data sets and Pega 7 Platform instances more easily with export and import operations. You can use the export operation to prepare a backup copy of data outside the Pega 7 Platform. The import operation facilitates initialization of new Pega 7 Platform environments by providing a prepared set of data. You can export data from the data sets that support the Browse operation, and you can import data into the data sets that support the Save operation. Export and Import operations are not available for stream data sets such as Facebook, Stream, Twitter, and YouTube.

For more information, see Exporting data from a data set and Importing data into a data set.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us