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.

Tomcat log files moved to work directory

Valid from Pega Version 7.1.2

For Tomcat application server users, the default path for PRPC logs has been changed to the "work" directory for Catalina. For example:

<tomcat>\work\Catalina\localhost\prweb

This directory can be cleaned up during administration. To avoid loss of files, you can redirect logging to a different directory after installation:

  1. Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
  2. Open the prlogging.xml file.
  3. Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
  4. Update the FileNamePattern values to point to the new directory.

For more details, refer to the “Change the default path to PRPC logs” section in the Tomcat installation guide for your database.

Guardrails compliance score

Valid from Pega Version 7.1.5

The Application Guardrails landing page has been enhanced to help you build more guardrail-compliant applications. Increase transparency and accountability on your projects by responding to the following compliance score metrics:

  • A weighted compliance score (0-100) based on warnings, severity, and justification
  • A percentage of compliant rules in your application
  • Total number of rules in your application
  • Total number of rules in your application with warnings (justified and unjustified)

Additional metrics include alert and interaction count trends over the last four weeks.

For more information, see Guardrails compliance score.

EAR support for JBoss EAP 6

Valid from Pega Version 7.1.5

PRPC deployment in JBoss EAP 6 as an EAR archive is now supported. 

If you need to deploy the JBoss EAR file, go to My Support Portal and submit a Support Request. GCS can assist you with the procedure.

Directed inheritance view in Application Explorer

Valid from Pega Version 7.1.5

You can now specify which inheritance model is used to populate classes in the Application Explorer. From the top level menu, use the “Explorer Inheritance” option to choose between:

  • Pattern: only display class names whose prefix matches the root node class name.
  • Directed: first display classes that explicitly name the root node as the parent class; then display classes with pattern inheritance.

108936_ExplorerInheritance.png

By default, the Application Explorer loads using Pattern inheritance. 

Small distribution kit

Valid from Pega Version 7.1.5

A new “small” release distribution format for Maintenance Levels (ML) is now available, designed to significantly increase adoption via: 

  • Minimal package size and faster download time
  • Minimal install time via tactical changes to the upgrade implementation and process

This kit contains streamlined installers (both UI and command-line installers) and specialized error handling for ML updates (for example, a “small” kit will only work if an existing version of the same release is already installed). 

The kit assembly has also been automated, which includes the construction of a PRPC_Rules.jar archive containing cumulative rules since the GA release. 

A “small” kit will work for any prior ML release within a major release (for example, the “small” ML5 distribution kit will update any customer on 7.1 ML1 through 7.1 ML4).

Improved data page performance

Valid from Pega Version 7.1.5

Improvements have been made with queueing and processing of asynchronously-loaded data pages to reduce the number of calls to the database and avoid generating performance problems because of unneeded asynchronous requests.

Save Application Explorer filter selections

Valid from Pega Version 7.1.5

Application scoping control selections made in the Application Explorer are now persisted between sessions. These preferences are stored in an operator record on an access group level. If you delete (and later re-add) an access group on your operator form, the application scoping control defaults to all layers selected:

109056_AppScopingControl.png

External access control DASS

Valid from Pega Version 7.1.5

A new Dynamic Admin System Setting (DASS) controls the Designer Studio's access to external systems, specifically the PDN RSS feed found on the home page.

By default, Pega-Desktop.AllowAccessToExternalSystem is set to TRUE. Update this setting to FALSE to hide the PDN RSS feed and ensure that no RSS fetch is performed.

Support for Data streaming service for Pega Cloud Marketing 7.4 applications

Valid from Pega Version 2.1

Pega Cloud Marketing 7.4 applications support the Kafka-based Stream service featured in Pega Platform 7.4.

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