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:


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.

System Management

Valid from Pega Version 7.1.3

The PRPC installer has been enhanced to handle additional error conditions related to partial installs and duplicate keys; additionally, the hotfix rollback feature has been improved, and the Rulebase compare tool now supports HTTP(S) environments.

  • Rollback feature has been enhanced.
  • RuleBase Compare will work for secure (HTTPS) environments as well as  non-secure (HTTP) environments.
  • Install will gracefully handle the presence of a duplicate key during import.
  • When install fails, system will set tables back to original state.
  • Remote MBean methods will now work on multi-servant load-balancing systems.
  • Enhancements were made to harnesses in Split Schema systems.

Adaptive Decision Manager installation changes to support delayed learning

Valid from Pega Version 7.1.7

To support delayed adaptive learning, Adaptive Decision Manager (ADM) has been enhanced with database schema changes and no longer relies on Hibernate. This change has an impact in the way ADM is set up in the Decision Management service layer: the jdbc/admDataSource resource is now superseded by jdbc/adm7DataSource.

Additionally, Pega 7.1.7 further simplifies the ADM deployment by providing a single enterprise application or web archive:

  • Single EAR deployment archive that can used when deploying ADM on IBM WebSphere and Oracle WebLogic
  • Single WAR deployment archive that can be used when deploying ADM on Tomcat and JBoss

Improved full text search

Valid from Pega Version 7.1.7

In Pega 7.1.7, Elasticsearch is used to provide full-text search functionality for rules, work, and data content, replacing the existing Lucene search functionality. In addition to providing search results two to five times more quickly than with Lucene Search, Elasticsearch is more scalable: with multi-threaded bulk and incremental indexing, it provides enhanced information about the search queue, the ability to host index files on multiple nodes, a more robust and expressive search parser, the ability to configure thresholds for alerts and search query time-outs, and automatic handling of replication and failover.


The search management user interface, where you can see length of queue and age of entries, which node hosts the search index, and where it is located.

After upgrading to Pega 7.1.7, the system administrator must manually migrate search functionality from Lucene Search to Elasticsearch. Note that during the switch-over and until the indexes are rebuilt, Lucene search continues to function and there is no interruption in search functions. For more information, see the Pega 7.1.7 Upgrade Guide.

View agent activity and status more efficiently

Valid from Pega Version 7.1.7

The Designer Studio > System > Operations menu has been updated with several additional tabs detailing system information pertinent to an active server node running on a system, along with its requestors, log utilities, and purge/archive utilities. The link to the System Management Application tool has also been moved to the Designer Studio > System > Operations menu in this release.

Previously, to understand your system, you had to access every node on your system individually. With this update, the information available on these tabs allows you to view all agents across a cluster to determine if an agent is active and in-depth details about the agent in a more efficient manner.


The System: Operations page displays agent information and status on a system

Access this menu by selecting Designer Studio > System > Operations. For more information, see the System Operations landing page.

Changes to default Agent settings

Valid from Pega Version 7.1.7

Default agent settings across several rulesets have been updated in this release. Changes to settings include agents that are now:

  • Disabled by default
  • Scheduled to run at a recurring designated time interval (in seconds)
  • Scheduled to run daily at a specified time


An example of some updated default agent settings. Compared to earlier versions, you can see in Pega 7.1.7 that ProcessCaseTypeCalculations and ProcessFlowDependencies are now set to run every 60 seconds, and that ProcessEmailRequest is disabled.​

​​This update allows operations staff to understand the general purpose of an agent by product, and enhances usability of this information by improving navigation of agents in large systems through filtering and sorting.

For more information, see Changes to default agent settings in Pega 7.1.7.

Application Validation boosts productivity without ruleset prerequisites

Valid from Pega Version 7.1.7

By default, Application Express leverages the new Application-Based Validation (ABV) mode for a more flexible development experience without having to use ruleset prerequisites as is required with Ruleset Prerequisite-Based Validation (RSP) mode, which remains available and supported.

With RSP mode, a list of prerequisites might differ from your runtime list, which could lead to behavior differences between validation and runtime. This prerequisites list was hard to maintain and could change unintentionally, often leading to unpredictable results. With the addition of ABV rulesets, however, you now have the ability to reference all rules in rulesets defined in the same application and rulesets belonging to any built-on application.


In this example of an ABV ruleset, each shaded or unshaded cell represents an application, and each name represents a ruleset. With ABV, you have the ability to call rules both above and below the designated ruleset.

Select Application Validation mode to validate rules without having to specify prerequisites.


By default, the generated framework and implementation rulesets use Application Validation instead of explicit ruleset prerequisites.

For details on how ABV determines which rules are valid to reference at design time, see Understanding Application-Based Validation mode.

Check validity of rules in application with Validation tool

Valid from Pega Version 7.1.7

When you update your application definition, there are certain changes that can invalidate some of your rules. Use the new Designer Studio > Application > Validation tool regularly to ensure that all rules referenced in an application have valid rule references based on the application context.

This simple tool can quickly help you improve the quality of your application and should be used regularly. For example, if you delete or change the return type of a rule, by running the Validation tool, you will know how many rules became invalid by that change.


When you run the Validation tool from the Designer Studio menu, a progress bar indicates your progress.

For more information about when to run the Validation tool and how this solution can confirm that rules pass current validation requirements, see About the Validation tool.

Optionally reverse update to return to original version

Valid from Pega Version 7.1.7

You can now roll back to a prior release after performing an out-of-place, split-schema update on a Pega 7.1.7 development system. For example, you can update from Pega 7.1.5 to 7.1.7, and then reverse the update to return to 7.1.5.

For more information, see the Maintenance Level Update - Deployment Guide.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us