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.

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.

Access Manager portal

Valid from Pega Version 7.1.5

Changes to the Access Manager simplify the process of modifying the access rights of features for an application. The changes, including creation of an Access Manager portal, make it easier for non-technical users, such as business architects, to set access rights even if they may not have a deep understanding of Pega 7's security model and class inheritance structure.​

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.

Restricted SMA access

Valid from Pega Version 7.1.5

System Management Application (SMA) remote connections are not supported on JBoss EAP 6.x. This means SMA users may only monitor locally connected systems. Ensure that the "Local JVM Connection..." option is selected when configuring PRPC nodes:

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.

Application Express and the Content Security Policy

Valid from Pega Version 7.1.7

Application Express copies (if defined) the Content Security Policy (CSP) name (pyContentSecurityPolicyName) from the built-on application in a new application. It also sets the CSP mode (pyContentSecurityPolicyMode) to report. The values appear in the Content Security area on the application rule's Integration & Security tab.

When checking an application in the DCO Compatibility tool, a warning appears if the CSP name is missing.

DB2-LUW database logfile size increase

Valid from Pega Version 7.1.5

This issue applies to DB2-LUW database platforms only.
 

To avoid running out of logfile space due to large transaction sets during the rule base load of a Pega 7.1.x install, upgrade, or maintenance level update, systems supported by a DB2-LUW database platform should increase the LOGFILSIZ parameter to at least 4096 pages from the default size of 1000 pages.

After the size has been increased, restart the database to ensure that the new setting is loaded into the database correctly.

Unable to drop triggers for frameworks with custom rule tables

Valid from Pega Version Pega Platform

For PostgreSQL and z/OS systems, if your deployment includes a framework or application with custom rule tables (such as CPM or any applcation built on CPM), upgrading to Pega 7.1.x causes the DDL application to fail when it tries to drop the following stored procedures:

  • z/OS
    • SPPR_RULE_VW_UPDATE
    • PRPC_UPDATESCACHE
  • PostgreSQL
    • sppr_base_uc_del.sql
    • sppr_base_uc_ins.sql
    • sppr_base_uc_upd.sql
    • sppr4_fv_ins
    • sppr4_fv_upd

During an upgrade, a number of stored procedures must be dropped and re-added. If the framework or application has custom dependencies that call the stored procedure, this problem is likely to occur.

To correct this issue, drop the framework’s custom dependencies before upgrading and add back the dependencies following the upgrade.

For instructions about how to drop and add the dependencies for your framework and database when this problem occurs, see Troubleshooting: PRPC 7.1.6 upgrade does not drop PRPC_UPDATESCACHE stored procedure.

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

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