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-B44278 · Issue 302830

MT guide updated for rules blocking/restriction

Resolved in Pega Version 7.3

The MultiTenant guide has been updated to clarify what causes rules to be blocked or restricted and the possible consequences of unrestricting rules.

SR-B48780 · Issue 305215

Oracle/Unix documentation updated with JDBC instructions for urandom instead of random

Resolved in Pega Version 7.3

The Install/Upgrade guides have been updated to reflect that recent changes to Oracle have created the requirement of forcing the JDBC driver to use /dev/urandom instead of /dev/random to improve security as well as connection open and close performance. The guide now recommends customers running Oracle on Unix do one of the following: 1. Update $JAVA_HOME/jre/lib/security/java.security to use securerandom.source=file:/dev/./urandom 2. Set system property -Djava.security.egd=file:///dev/urandom

SR-B8847 · Issue 278000

FCM/FCMR documentation updated

Resolved in Pega Version 7.3

The documentation on the PDN for installing and configuring FCM 7.12 has been updated for FCM and FCMR.

SR-B8898 · Issue 279449

Reference to outdated property removed

Resolved in Pega Version 7.3

When building a system with WebSphere 8.5.5, DB2 10.5fp7 and Java 8, creating the environment and testing the connection on its datasource produced the warning: "DSRA8200W: DataSource Configuration: DSRA8020E: Warning: The property 'progressiveLocators' does not exist.". This was traced to a code fragment left after that property became unsupported which has now been removed.

SR-D62754 · Issue 559848

PrepareResponse updated to explictly close Input Handler

Resolved in Pega Version 8.2.7

When using prpcServiceUtils to export a product in a Windows+Weblogic environment, attempting to export repeatedly using the same archiveName with the intention of overwriting the older product with the newer one in the ServiceExport directory failed with a FileNotFoundException. Investigation showed that the product file that was created by the pzExport REST call was not being released by the Weblogic File Handler process. Due to this, the next time the call was invoked the system tried to create the same file in the directory but failed due to the earlier File handle lock. To resolve this, the system has been updated to explicitly close the InputStream using try-with-resources.

SR-D78274 · Issue 544092

Handling added for dual privileges with MSSQL

Resolved in Pega Version 8.2.7

After setting up dual privileges, the Admin user was able to create a table but the base user received an "insufficient privileges" error. Investigation showed this was an issue when using MSSQL: the generated grant statements used the server login name as the user in the grant statement, instead of the database user. For all other databases, the username passed into the connection is the correct user to use for grants. Only MSSQL has a distinction between this connection user name (the login) and the database user, and since the login did not exist in the user table, the grant failed. To resolve this, when MSSQL is used, the system will fetch the underlying database user when determining the user for grant statement generation.

SR-D84190 · Issue 547173

Post-Import Migration Agent query optimized

Resolved in Pega Version 8.2.7

A Post-Import Migration agent belonging to the Pega-ImportExport Ruleset and set to run every 60 seconds by default triggered the SQL query "select ASTERISK from pegadata.pca_CWT_CXP_Work_Interaction" which ran for an excessive amount of time, caused a utilization spike, and then crashed the utility nodes. Investigation showed the excessive run time and load was caused by the query fetching a very large number of results. To better handle this scenario, the query usage has been updated.

SR-D84364 · Issue 551400

Check for circular references added to SearchInventoryImpl to prevent recursive call

Resolved in Pega Version 8.2.7

An out of memory error was traced to SearchInventoryImpl infinitely recursing over a clipboard property, where the child property referenced a parent property and resulted in an endless loop. This has been resolved with the addition of a depth check to ensure that the search does not recurse infinitely.

SR-D85100 · Issue 556260

ProductInfoReader updated to fetch only most recent version information

Resolved in Pega Version 8.2.7

After update, running Hfix scanner on Pega Marketing 8.2 displayed missed critical Hfixes for Pega Marketing 8.1. This has been resolved by modifying ProductInfoReader.runQuery to fetch only latest version of DAPF instances during a scan.

SR-D90687 · Issue 560427

IOException handling improved to resolve broken pipe errors

Resolved in Pega Version 8.2.7

Frequent "connection reset by peers" exceptions were being generated and broken-pipe exceptions were seen in the logs. Investigation traced the issue to unhanded IOExceptions on the server side that were a result of the client application not always closing the TCP connection gracefully. To resolve this, error handling for IOExceptions has been improved.

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