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.

New mobile capabilities in Pega Express

Valid from Pega Version 7.2

In Pega Express, you can now configure offline case types and quickly build a custom mobile app from the Mobile app tab in the settings. You can apply branding, use certificates, and take advantage of device capabilities such as geolocation tracking. If you set up signing certificates (Android, iOS) and provisioning profiles (iOS) for the custom mobile app in the Designer Studio, you can also access them in Pega Express.

For more information, see Building mobile apps.

Improvements for the PMML models

Valid from Pega Version 7.2

The Pega 7 Platform extends support for the PMML models to include PMML 4.2 features and validations. Additionally, the PMML files that contain custom functions can be imported into the Pega 7 Platform and used in strategies.

For more information, see Predictive Model rule form.

Relevant records to define reusable assets

Valid from Pega Version 7.2

Relevant records describe the collection of rules that refine the behavior, presentation, and definition of a case or data type. They are commonly used to designate records from an inherited class as important or reusable in a child class.

Use relevant records to define information displayed in certain Pega 7 Platform application screens and fields. The Pega 7 Platform provides a number of items marked as relevant records, and you can further manage relevant records for your own case and data types.

For more information, see Relevant records.

Data Flow rule enhancements

Valid from Pega Version 7.2

The enhancements to the Data Flow rule facilitate decision execution in real time, batch, and Pega 7 Platform applications. The DataFlow-Execute method in activities can be used to execute and monitor batch runs and real time data flows. In addition, you can configure pre- and post-activities that are executed before and after data flow execution.

For more information, see the following Pega 7 Platform help topics:

Stage-based revision and change request management enhancements

Valid from Pega Version 7.2

The revision and change request processes are based on the case management capabilities provided by the Pega 7 Platform. The customizable flows that controlled the behavior of the revision and change request management (pyManageRevision, pyManageChangeSet, pyApproveChangeSet, and pyDirectDeployment) are now part of the Revision and Change Request case types that govern the behavior of revision management. The change from flow-based to stage-based revision management makes the process more transparent and easier to modify.

For more information, see Stage-based revision and change request management.

Improvements to the HBase data set, HFDS data set, and Hadoop host configuration

Valid from Pega Version 7.2

The Pega 7 Platform features maintenance improvements to the Hadoop host configuration, HBase data set, and Apache Hadoop File System (HDFS) data set. System architects can more easily make HDFS and HBase storage available to business scientists for exploratory analysis and predictive model building.

For more information, see Big data functionality enhancements.

Improvements to Visual Business Director (VBD)

Valid from Pega Version 7.2

Business monitoring and reporting no longer depends on the external Visual Business Director service because VBD is now embedded in the Pega 7 Platform. You add a VBD node to the cluster to access VBD for simulations and monitoring. In addition, when you use the Google Chrome browser, VBD launches as a new HTML client that provides the visualization.

For more information, see The Visual Business Director (VBD) HTML client and Accessing Visual Business Director (VBD).

Use multiple built-on applications to enhance ruleset reuse

Valid from Pega Version 7.2

Applications can now have multiple built-on applications, allowing rules to be reused as a part of a built-on application at run time while being developed independently at design time.

Previously, applications built in Pega 7.1 and earlier versions were assembled in a single linear application stack--one application built on top of another application, and so on. Attempting to reuse rulesets and frameworks across applications resulted in having to splice applications together, creating challenges when attempting to support the use of these custom created applications. Starting in Pega 7.2, applications are built on to other applications by using a hierarchical tree structure, and the Pega 7 Platform automatically converts this tree into a linear application stack.

For more information, see Using multiple built-on applications and the Ruleset behavior at design time section in Application stack hierarchy for multiple built-on applications.

Import specifications

Valid from Pega Version 7.2

In Pega Express, you can now import specifications from an Excel spreadsheet. Keeping specifications up-to-date helps you to generate a meaningful application profile document to share information about your project with stakeholders.

For more information, see Importing specifications.

Create and edit reports

Valid from Pega Version 7.2

In Pega Express, you can now create and edit reports for the case types in your application. You can use the new reporting features to modify the way information is displayed in a report and to sort and filter the data for different audiences.

For more information, see Creating reports and Editing reports.

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