Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A22147 · Issue 244096

Autogenerated prconfig sets v6 or v7 based on detection

Resolved in Pega Version 7.2.1

The autogenerated prpcUtils prconfig.xml file was setting the database/storageVersion to 6. In order to facilitate other setups, a flag has been provided in prpcUtils.properties as pega.storageVersion which will set the value in generated prconfig.xml to an empty string so the engine handles setting this to 6 or 7 in the same way that is possible when running the system.

SR-A22263 · Issue 242102

Improved error reporting for PE install

Resolved in Pega Version 7.2.1

In order to facilitate debugging, attempting to install Pega Express from a directory with a space in the name will generate an error on the screen reiterating the installation instructions requiring that the directory name not contain a space.

SR-A22354 · Issue 245861

prpcUtils honors 5.4 compatibility checkbox

Resolved in Pega Version 7.2.1

Pega deployment using prpcUtils was failing due to the 5.4 compatibility checkbox being ignored: the product rule being exported still included schema changes in the exported RAP file. This has been corrected.

SR-A22672 · Issue 243213

Use Pega Log Analyzer in place of Alerts.xls Excel Template

Resolved in Pega Version 7.2.1

A documentation error incorrectly referred to the Alerts.xls Excel template as being available on the PDN. That file is no longer available, and the Pega Log Analyzer should be used instead: https://pdn.pega.com/community/pega-exchange/pegarules-log-analyzer

SR-A23134 · Issue 243870

Resolved upgrade exception caused by non-standard requestor setting

Resolved in Pega Version 7.2.1

Upgrading to v7.2 was failing if the 'Requestor Types' (DATA-ADMIN-REQUESTOR instances) ACCESS GROUPs had been modified in the previous version for the System Name 'prpc'. This modification caused the PRPC requestors to not be replaced during upgrade. To address this issue, the installation will create a RAP to import into the SDE that will check for this condition, and the PRPC Requestors have been updated such that they cannot be modified. See also: Process Commander V6 help "About Requestor Type data instances" and "When and how to change a system name" for more background information about Requestor Types.

SR-A23339 · Issue 247921

Non-versioned class rule forms updated during upgrade

Resolved in Pega Version 7.2.1

The non-versioned class rules in an environment were skipped during upgrade due to an error in the RevalidateAndSave function. This has been corrected.

SR-A23979 · Issue 246353

Revamped help docs to clarify ServiceExport directory config

Resolved in Pega Version 7.2.1

An error in the help documentation did not correctly outline the method for changing the ServiceExport directory by modifying prconfig.xml. The directory location is hard coded to StaticContent/global/ServiceExport in the temporary directory, but the location of the temporary directory is configurable using the Initialization/explicitTempDir setting. Changes have been made to the help files to clarify this.

SR-A24052 · Issue 248427

Orphaned work objects purged by class

Resolved in Pega Version 7.2.1

Orphaned work objects were not purged when their parent was deleted from the database. To resolve this, selecting a Work- object class for purging will also purge all of the orphans in that class.

SR-A24478 · Issue 247983

Diagnostic logging added to upgrade Java Syntax task

Resolved in Pega Version 7.2.1

While running the upgrade.sh script to upgrade an in-place single-schema upgrade, the script halted while performing "Scanning Class" operations and remained there for over 8 hours. Attempting to resume appeared to proceed for a few minutes before halting again and remaining at the same point. The problem was traced to list views getting the PMD going into an infinite loop during the upgrade java syntax task. Diagnostic logging has been added to the PreUpgradeRuleAnalyzer/JavaParser code to add a log statement to print any keys which are getting processed when errors occur.

SR-A24517 · Issue 246951

JMX Javadoc available for download

Resolved in Pega Version 7.2.1

The document MBeanJMXJavadoc.zip was last shipped in Pega 7.1.7 and was not present in the on-line documentation. The Mbean Javadoc package is now available for download at the following link: https://pdn.pega.com/release-note/mbean-javadocs-download-file

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