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.

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.

PRServlet not required in PRPC URLs

Valid from Pega Version 7.1.6

PRServlet is no longer required in a URL when accessing PRPC. A URL typically written like this:

http://example.com/prweb/PRServlet?[QueryString]

Can instead be written like this:

http://example.com/prweb/?[QueryString]

This change is effective only for PRPC 7.1.6 and newer versions. Older versions of PRPC still require using PRServlet in a URL.

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.

Add additional columns to customized work history tables

Valid from Pega Version 7.1.6

The standard work history table, pc_history_work, contains two new columns that return the latitude and longitude coordinate location of the action that prompted the history. Mobile devices can display this location as a street address. If you have a customized work history table, add these two columns to it:

  • <decimal name="pxLatitude" size="19" scale="9"/>
  • <decimal name="pxLongitude" size="19" scale="9"/>

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