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.

Reporting

Valid from Pega Version 7.1.3

This release had a focus on extending key capabilities to improve the functionality and ease of use of reporting features based on early adopter feedback.  A series of cosmetic changes and fixes are also included.

  • Multiple boxes may be checked on List view checkboxes
  • Dashboard Charts slider has been improved.
  • Summary View reports and charts have been enhanced.
  • Column properties can be added to a report in the Report Editor.
  • List view column widths can be set by Smart Info.
  • Listviews will display correctly for updated systems.
  • Improvements to the GuardRail Report.

Report Viewer provides simplified user experience

Valid from Pega Version 7.1.7

In the Report Viewer, improvements simplify the user experience when working with reports. Column headers display initial sort order and type, and you can hover over a column header to display and use its context menu, which includes options for ad-hoc sorting and filtering. Developers can specify various pagination modes and set an option to keep the header in view while users scroll through the report.

For more information, see Report Viewer.

Enhanced BIX file naming

Valid from Pega Version 7.1.7

To help clarify file names, BIX extract output files and manifest files can now contain parameters. Parameters can include the rule name, the extract's run time and date, and a unique run sequence number. Special characters such as spaces, hyphens, or number signs (#) in the output or manifest file name are converted to underscores. In addition, the pxExtractIdentifier and pxExtractDateTime columns have been added to the .csv output file.

For more information, see Extracting data with BIX and Extract rules - completing the File Specification tab.

Enhanced chart control improves displaying data as a chart

Valid from Pega Version 7.1.7

The renewed chart control has an improved properties panel and provides HTML5-compliant pie, column, bar, area, line, and gauge charts. The chart source can be a report definition, a clipboard page, or a data page. You can customize basic and threshold colors, borders, line widths, labels, and other chart elements. A preview on the property panel instantly displays the effects on the chart of property changes you make.

For more information, see Harness and section forms - Adding a chart.

HTML5-compliant chart types

BIX performance improvements for CSV output in the Pega Cloud

Valid from Pega Version 7.2.1

BIX performance has been enhanced to download up to 25 GB of data per hour for extracts from a BLOB-less class table for CSV output. This high-throughput option is available only for Pega Cloud instances that use a Postgres database. This option is used automatically for these types of extracts.

When this option is used, the –x and –c command-line options for BIX are not supported, and the checkSum field in the manifest summary is not populated. If you need these options, you can revert to the previous implementation by using a setting in the prconfig.xml file.

For more information, see BIX high-throughput data downloads in the Pega Cloud.

Push notification delivery to multiple devices

Valid from Pega Version 7.2.1

Push notifications sent from the Pega 7 Platform are now delivered to all devices on which a user is logged in to your custom mobile app, regardless of the device platform. You can either send push notifications from the Push Console to all users who have your application installed on their devices, or configure your application to send push notifications to indicate that an action might be required, a status update is available, or a case was approved.

Support for subflows and decision flow results in offline mobile apps

Valid from Pega Version 7.2.1

Subflows in offline-enabled mobile apps are now supported to perform additional tasks outside of the main flow. The subflow can run only on the current work item, with the subflow displaying in the main flow, in a nested subflow, or located next to an assignment. No likelihood routing is supported for subflows. It is also possible to set a flow result by using the pega.process.flow.setFlowEndStatus() JavaScript method to override the status set by a property in the subflow's end shape. The process engine also takes into account the likelihood setting if the flow result is conflicting or absent, provided the flow result is not in a subflow.

For more information, see Flow processing in offline mode.

Support for error handling API in offline mobile apps

Valid from Pega Version 7.2.1

During the processing of cases in offline-enabled mobile apps, you can use several JavaScript API methods to perform error handling. You can now determine whether an error condition results from the post-processing of a flow or a subflow. You can also set, clear, or obtain the number of error messages on a property or a page while working in offline mode, similar to when you are running a Pega 7 Platform desktop application. When you run a custom mobile app in offline mode, you can submit a form, but you cannot move the flow forward until all the errors on a page and in the page's properties are resolved.

For more information, see Error handling in offline mode and Error handling API in offline mode.

Application administrators can send push notifications

Valid from Pega Version 7.2.1

From the Push Console application, administrators can send push notifications to custom mobile app users. Notifications sent from the Push Console can contain application-wide messages, for example, when an update is available for manual download.

For more information, see Push Console landing page.

Transition effects for actions in custom mobile apps

Valid from Pega Version 7.2.1

Custom mobile apps that are developed on the Pega 7 Platform can include built-in transition effects that animate your forward or backward movement in cases that use flows. This feature adds to the look-and-feel experience of the custom mobile app.

You can also manually add a transition effect to actions that do not support built-in effects by using the Run Script action and calling the pega.desktop.setNativeTransition() JavaScript method.

For more information, see Transition effects on actions.

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