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.

SR-D90687 · Issue 560431

IOException handling improved to resolve broken pipe errors

Resolved in Pega Version 8.4.2

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.

SR-D67408 · Issue 554900

Directory traversal blocked in zip import

Resolved in Pega Version 8.4.2

One of the files contained in a zip archive was not deleted from the system after zip import. This was due to the file being created by a third-party archive that included of a directory traversal character that caused it to be inflated outside of the temp directory. To resolve this, a check has been added to that a file with directory traversal characters in its name will not be inflated.

SR-D81572 · Issue 551028

JDBC URL handling added for Oracle over TCPS

Resolved in Pega Version 8.4.2

While attempting to upgrade an environment over TCPS, the generateDDL.sh script was failing. The same environment ran without issue on Tomcat with the same URL. Investigation showed the JDBC url was not correctly generated while running the upgrade: in a standard scenario, there will be no spaces in the JDBC URL specified. However, because Oracle can send spaces as part of JDBC URL and cause this issue, an update has been made which will quote the JDBC URL argument for the ant target in setupDDL.xml.

SR-D84364 · Issue 551403

Check for circular references added to SearchInventoryImpl to prevent recursive call

Resolved in Pega Version 8.4.2

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 556262

ProductInfoReader updated to fetch only most recent version information

Resolved in Pega Version 8.4.2

After upgrade, 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-D98404 · Issue 558207

Handling added for hotfix Rule-Application instances

Resolved in Pega Version 8.4.2

A null pointer error during DL file expansion performed as part of the second phase of a hotfix installation caused the hotfix install to fail. The null-pointer exception was thrown because the code, primarily used for export, performed a database lookup of a Rule-Application and assumed the response would be non-null without checking the result. During export the Rule-Application would normally exist because the system would have interacted with it already during the export by identifying it and writing it to the archive. During phased hotfix installation, rules are staged to the database in a different table during the first phase and reconstituted during the second phase. The scenario for this error was a missed corner case specific to the unusual combination of including Rule-Application instances in a platform hotfix. To resolve this and prevent further issues, handling has been added for this use case.

SR-132637 · Issue 203591

Added path checking to FirstLogCreationTime.log

Resolved in Pega Version 7.1.9

FirstLogCreationTime.log was being written to a temp folder using hard-coded logic to use a relative path within the install directory. This caused errors if the installer was trying to write the logs in an absolute path. FirstLogCreationTime.log should be written to the same directory as the rest of the logs, and this issue has been fixed by adding a condition in LogDeleteUtil.getLogCreationTimeFile() method to check for absolute paths.

SR-132720 · Issue 203636

Resolved stale transaction error on editing operator skills

Resolved in Pega Version 7.1.9

After creating a control that displayed a listview of operators in a side panel with a single click event on the list view to show a button, clicking the button was intended to open an out-of-the-box html rule "ShowSkills" which is used to show/update the skills of the operator. However, on the "ShowSkills" screen the error "This action is not allowed as it is outside the current transaction" was being generated when trying to update the operator skills. This was caused by a stale transaction error, and has been resolved by adding the type 'button' on the buttons in the ShowSkills HTML code.

SR-133040 · Issue 203518

Removed duplicate special character encoding on FieldValue validation

Resolved in Pega Version 7.1.9

A recent change was made to the "Validate" activity of the Rule-Obj-FieldValue class to improve security by performing a filterRichText (intended to remove unsafe tags like script tag). However, this broke a reported use case where field values used as the source for the controls dropdown, checkbox, or radio buttons displayed the encoded values of quotes due to double encoding. To fix this, the filterRichText step has been removed from Rule-Obj-FieldValue!validate activity.

SR-133501 · Issue 202754

Error icons and localization corrected for repeating tabs headers

Resolved in Pega Version 7.1.9

The error message indication was not appearing on the tab header of repeating tabs. In addition, the tooltip of that icon was not being correctly localized. These issues have been corrected.

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