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.

INC-211480 · Issue 712419

Handling added updates involving Oracle descending column

Resolved in Pega Version 8.6.4

The build was failing when attempting to update to Pega 8.6, and an error indicating an issue with Oracle columns was generated. Investigation showed that when a column changed that belonged to an index which had a 'desc' column (even if the changed column was not specified as desc), an Oracle restriction was triggered. This occurred with any column size increase if the column participated in an index containing a descending column or a function index. This has been resolved by adding a step to drop the index before altering the column if a Descending index is involved, and to catch the case where the resized index is part of an index that has a descending column but is not necessarily a descending column itself.

INC-211599 · Issue 708542

Data page definition reload made more robust

Resolved in Pega Version 8.6.4

The data page was intermittently being removed from the cache. This was traced to the use of a thread from ThreadContainer to reload the data page definition: a null thread could be returned if the request came from a master agent, which would then cause the definition reload to fail. This has been resolved by updating the system to use the current thread in context to reload the data page definition.

INC-212729 · Issue 695025

ClusterAndDBCleaner updated to with with Oracle query limits

Resolved in Pega Version 8.6.4

The pzClusterAndDBCleaner job scheduler was not able to cleanup data in pr_op_data session table due to the delete query formed to clean up this table throwing "ora-01795 maximum number of expressions in a list is 1000 oracle 19c" exception. This has been resolved by splitting requestor IDs into batches of 1000.

INC-212900 · Issue 711001

ADLS/File listener support added

Resolved in Pega Version 8.6.4

Azure Data Lake Storage type support has been added for file listener usecases.

INC-213308 · Issue 712075

Fallback added for missing fileName in MultipartHTTPResponse

Resolved in Pega Version 8.6.4

Given a multipart/form-data response with multiple attachments, when there was no explicit fileName header provided for a body part, the engine skipped processing the part and no data was present on pyRequestAttachmentPage. This has been resolved by adding a fallback in HTTPClientUtils#handleMultipartHTTPResponse() so that if no fileName is present, the 'name' parameter of the Content-Disposition header field will be used.

INC-213502 · Issue 711797

Updated context handling for DxAPI Perform Assignment lock

Resolved in Pega Version 8.6.4

The DxAPI Perform Assignment was generating the error "ValidationMessage:Unable to unlock GROUP-DISPUTES-WORK". This has been resolved by adding an update to ensure proper context is set for getting an additional lock handle.

INC-213808 · Issue 710298

Stability enhancement to improve platform reliability and resiliency

Resolved in Pega Version 8.6.4

During a NBA campaign run, the data flow partition became stuck in the in-progress status and the campaign run did not complete. NoClassDefFoundException errors were logged, indicating a connectivity issue with the database after which the node was not able to recover successfully. This has been resolved by adding an enhancement to better handle situations where a database outage is detected.

INC-172944 · Issue 662828

Skin rule circumstancing article added

Resolved in Pega Version 8.6.4

An article on skin circumstancing best practices has been added to https://collaborate.pega.com to aid in working with this functionality.

INC-176462 · Issue 657412

Dashboard widget drilldown section adjusts dynamically

Resolved in Pega Version 8.6.4

While trying to expand the drilldown columns, text was overlapping due to the grid not adjusting the large size of data dynamically. This was traced to an unnecessary CSS rule being applied to set max-height which broke the styling. This has been resolved by removing the height limitation on detail cells.

INC-180100 · Issue 662894

Scrollbar persists for multiselect

Resolved in Pega Version 8.6.4

Selecting more than 20 values in the multiselect control caused the scrollbar to disappear. This has been resolved by removing a custom popover height calculation.

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