Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number 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.

INC-119803 · Issue 561684

Placeholder text added for question dropdown sourced by a datapage

Resolved in Pega Version 8.3.4

In a flow action with question pages where each question page was configured with a set of question rules, one question which displayed a country list in a dropdown sourced from a datapage always displayed the first value by default in the dropdown instead of place holder text (like Select..). In addition, the default selection value of the dropdown was not saving to the clipboard on submission of the flow action, causing it to appear in the UI like the first value had been selected even though nothing was saved on the clipboard. These issues have been resolved by adding place holder text in pzSetQuestionStreamSimpleDynamicSelect for a dropdown with a datapage source.

INC-120326 · Issue 564434

Landing page refresh modified to avoid frequent reloads

Resolved in Pega Version 8.3.4

Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.

INC-126114 · Issue 562176

Spaces member count method updated

Resolved in Pega Version 8.3.4

When a space contained more than 50 members, it always displayed the count as 50 even though the Spaces section showed the correct count. This was due to a pagination setting that had a maximum of 50 records set, and has been resolved by using the GroupMemberCount DP instead of AllMembers to retrieve an accurate count.

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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us