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.

DCO

Valid from Pega Version 7.1.4

This release focused on improving the user experience of creating new rules and tightening up the use of specifications in the Case Designer.  The layout of the New and Save As forms were made more intuitive and intelligent.  Specification actions were made to be more consistent across various aspects of the Case Designer.

  • After removing specification references, users can create and save a new specification.
  • Developers may now choose either an existing specification or create a new one for subflows and Split-For-Each shapes.
  • If a specification is not associated with flow shapes such as sub flows, Utilities, or Split-For-Each, it is possible to import speciications with the same names, and the flow shapes will default to using those imported specs.
  • In the outline view, specification changes will be preserved when switching from tab to tab.
  • The View Full Details functionality from either Configure Step or the Outline View will display all details, including the specification requirement links.

Reporting & Data

Valid from Pega Version 7.1.4

This release fixed many existing unlocalizable elements in 7.1 reporting interfaces (The Report Viewer, Report Editor, Chart Editor, and the Report Browser) and now they are fully localizable. Changes were made to make Listview, summaryview,  and report viewer display possible WCAG 2.0 level A and AA support.

  • Parameters may now be used in a sub-report join condition.
  • Report Definition localization has been enhanced.
  • Standalone ListViews with embedded SmartInfo have been improved to resize appropriately when the SmartInfo section is expanded.
  • The data section of a report will now display in all of the available space when a fixed header option is selected.
  • When localizing a listview with filters, tool tips are translated.

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.

Improvements to the Document Application tool

Valid from Pega Version 7.2.1

Application profile documents and application documents generated by the Document Application tool have been improved to present information in a more logical order based on how the application was built (for example, by case life-cycle management). Also, these types of documents now include all specifications linked with an implementation rule, presented in logical order under the implementation rule.

In addition, to help you more efficiently drive decisions by stakeholders, you can specify whether to include related built-on application layer assets in application profile documents and application documents. For specification documents, you can specify whether to include specifications from the built-on application layer.

For more information, see Document Application tool.

Add custom HTTP response headers in your application

Valid from Pega Version 7.2.1

The Pega 7 Platform supports the addition of custom security HTTP headers that are supported by your browser. For example, you can now create custom X-Frame-Options, X-XSS-Protection, and Strict-Transport-Security headers. These headers improve the security of your application against client-based attacks.

For more information, see Creating a custom application header

Associate specifications on implementation rule forms

Valid from Pega Version 7.2.1

You can now view, add, and delete the specifications that are associated with a rule on the new Specifications tab of most rule forms. The Specifications tab is available for almost all implementation rules, except for administrative and deprecated rule types. By associating specifications with the rules that implement them, you improve the end-to-end traceability of your specifications.

For more information, see Associating specifications on implementation rule forms.

Attribute-based access control model

Valid from Pega Version 7.2.1

Attribute-based access control (ABAC) is a security authorization model in which access rights are determined through the use of policies and attributes. A policy decision engine in ABAC evaluates digital policies against available data (attributes) to permit or deny access to the requested resource. For example, you can now determine access rights to cases by examining security attribute values assigned to the user and the case.

For more information, see Attribute-based access control.

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