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.

Customize your report headers

Valid from Pega Version 7.1.5

You can customize the way that the header for all of an application's reports will be displayed by overriding the section pyReportEditorHeader. Save a copy of this section into the application's ruleset, then edit it to display the information, images, and layout that you desire. Once changes are saved, each of your application's reports will automatically use the updated header.

Advanced inline report filters

Valid from Pega Version 7.1.5

You can create a custom section and use it to display report filter controls at the top of the report, replacing the default display. The custom section can include basic controls (such as a drop-down menu or text entry field), and the controls can only provide values for the filter functions established in the Edit filters section of the Query tab for the Report Definition.

Tracer supports SOAP messages

Valid from Pega Version 7.1.5

You can now select a Tracer Settings option to display SOAP connector and services messages in Tracer, which provides users with a better understanding of SOAP connector behavior.

Actionable error message in integration wizards

Valid from Pega Version 7.1.5

Improvements have been made to the integration wizards for SOAP, SAP, and .NET that enhance the user experience by providing clearer, actionable error messages when there are problems with WSDL uploads; letting you edit the endpoint while creating or testing the integration; clarifying how the data source class layer is reused and removing confusing terms; and adding an option in Tracer to view SOAP messages generated or received by integrations.

DCO and PMF integration is unavailable

Valid from Pega Version 7.1.5

DCO and PMF integration functionality is not available in this release. Related project management controls have been removed from the following:

  • System Settings landing page (Designer Studio > System > Settings > Project Management)
  • Application Profile landing page (Designer Studio > Application > Profile > Specifications)
  • Add/Edit Specification dialog

Use "alternate database" as report source

Valid from Pega Version 7.1.6

You can opt to use the the "alternate database" identified in the Reports Database field of the Data-Admin-DB-Table instance that supports the Applies To class of a report as the source for the report. This reduces the load on the database that serves your application when you run the report.

Attachment support for requirements

Valid from Pega Version 7.1.6

Requirements now support attachments. You can add attachments from the Designer Studio > Application > Profile > Requirements landing page, the Add/Edit Requirement modal, or the requirement rule form.

Enhanced document generation

Valid from Pega Version 7.1.6

The following usability improvements have been made to documents generated by the Application Document Wizard:

  • Stages and Processes now appear for case types that use Case Lifecycle Management. This diagram includes hyperlinks to corresponding sections in the document and is scoped to top-level processes only.
  • All flows (excluding pyStartCase) referenced by a case type now appear in documents. This removes previous constraints on non-starting, draft, and checked out flows.
  • Entity Relationship Diagrams (ERDs) are now embedded in documents as Visio objects.
  • Sections without content are omitted from the generated document.
  • Screenshots are labeled.
  • Requirement text (Long Description) is included in the Requirements Matrix section.
  • Linked requirements appear in context beneath their associated specification.
  • Acceptance Criteria appears in context beneath the associated specification, report, or correspondence item.

Create data page from REST integration

Valid from Pega Version 7.1.6

When you create a REST integration, you can choose to create a data page (and its related data type and data transforms) that can use the integration as one of its sources.

Use SAML 2.0 to provide single sign-on authentication

Valid from Pega Version 7.1.6

Configure a SAML 2.0 authentication service to provide web single sign-on (SSO) convenience to product users in your enterprise. A one-click option lets you import Identity Provider (IdP) metadata and make use of automated certificate management.

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