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.

INC-132859 · Issue 573491

ProductInfoReader updated to fetch only most recent version information

Resolved in Pega Version 8.4.2

Hfix scanner has been modified so that ProductInfoReader.runQuery will fetch only latest version of DAPF instances during a scan.

INC-123156 · Issue 560669

Check added for equivalent table during data upgrade

Resolved in Pega Version 8.4.2

The Data Upgrade between Pega versions failed with the error "DatabaseException caused by prior exception: java.sql.SQLException: ORA-01408: such column list already indexed". This was caused by the system not considering duplicate indexes before modified indexes. Once it's identified an index has been modified, the system would try to alter it without considering that what it was altering it to might already be present. To resolve this, an update has been made so the system will not alter an index if the resulting index would be equivalent to a different one on the table.

INC-125584 · Issue 559377

Warning logged when hotfix rollback information fails to save

Resolved in Pega Version 8.4.2

Attempting to apply a set of hotfixes was failing. In this case, a hotfix was being installed prior to a second hotfix which contained a Rule-Obj-Class that was needed for the first hotfix. Hotfixes need to be installed in a particular order based on their dependencies. For a given DL file, the installer respects the order specified at DL packaging time in the INSTALLORDER.PEGA file. The install order specified in the DL file is roughly ordered in a manner so that the first hotfix is the parent (the specific hotfix requested by the user at DL packaging time) followed by its dependencies in no particular order. The result was that dependencies of dependencies were not installed in the correct order relative to each other, causing hotfix installation to occasionally fail during the saving of hotfix rollback information. To address this failure, the exception handling has been modified to only provide a warning in the log should hotfix rollback saving fail and not cause the entire hotfix installation to fail.

INC-127460 · Issue 566413

SQL 'where' clause updated to handle Oracle limits

Resolved in Pega Version 8.4.2

Due to Oracle only allowing up to 1,000 IN list values in a SQL statement, a query exceeding that limit fails. To resolve this, the 'where' clause of the query has been updated to better handle this limit. The format is: WHERE col_name IN (val1, val2,……,val999) OR col_name IN (val1000, val1001,…)

INC-128758 · Issue 569896

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. In addition, the 50 result limit on executeRDB has been lifted to accommodate sites with more than 50+ Data-Admin-Product-Frameworks.

INC-133202 · Issue 574703

TableRenameUtil hashing improved

Resolved in Pega Version 8.4.2

During index name generation, the algorithm that was responsible for index name uniqueness was sometimes insufficient and cerated a loop condition. This has been resolved by using a stronger hash algorithm and refactoring the code that could result in a loop.

INC-71003 · Issue 555286

View/Modify Database Schema Wizard updated

Resolved in Pega Version 8.4.2

Security improvements have been made to the View/Modify Database Schema Wizard.

SR-D85653 · Issue 548600

Repaired Tracer use with Google Chrome

Resolved in Pega Version 8.5

After running Tracer while using Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Google Chrome Versions greater than 70 and was caused by Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead.

SR-D54319 · Issue 532528

API added to sync presence with requestor to clear inactive operator sessions

Resolved in Pega Version 8.5

An intermittent error message was seen indicating the maximum number of active sessions for the current operator had been reached even though there were not multiple logins and there was no requestor displayed in the requestor management landing page. This was traced to sessions that were not properly closed and cleared, and has been resolved by exposing an API that will sync the presence record with the requestor state so inactive sessions will be cleared.

SR-D64608 · Issue 544388

Corrected filedownload extension header issue

Resolved in Pega Version 8.5

Filedownload header contained plain non-ascii characters which caused a security violation issue. This has been resolved by removing the filedownload header from the HTTP response when the sendfile API is used with inputstream to download a file.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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