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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-211178 · Issue 704592

Decimal parameters retain null value instead of being set to 0

Resolved in Pega Version 8.7.2

When mapping any data in 8.6+, if the source is a decimal property rule and the target is a parameter defined as decimal, the decimal parameter's value will be 0 if the source property is null. This was a behavior change from previous versions of Pega where the target parameter would be null. This has been resolved by changing the code generation for the read operation on the parameter decimal type assignment to use resolveToString() instead of calling resolveToBigDecimal() so a null value is retained.

INC-211292 · Issue 705885

Updated handling for last_access to improve backwards compatibility

Resolved in Pega Version 8.7.2

After update from Pega 8.3 to Pega 8.6, many errors were seen in the logs regarding the call of the Pega API /api/v1/nodes/all/requestors. In 8.3, the API was responding with the field last_access populated properly, but this field was blank in the new version. This was an unintended consequence of work done to resolve inconsistencies with the date format in Admin Studio, and has been resolved.

INC-211480 · Issue 712418

Handling added updates involving Oracle descending column

Resolved in Pega Version 8.7.2

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 708543

Data page definition reload made more robust

Resolved in Pega Version 8.7.2

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-211655 · Issue 714059

Removed extra space in Malaysian locale

Resolved in Pega Version 8.7.2

For the ms_MY locale, an extra space was being appended to Number formats, such as " 0", " 1". This has been corrected.

INC-212729 · Issue 705111

ClusterAndDBCleaner updated to with with Oracle query limits

Resolved in Pega Version 8.7.2

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-213308 · Issue 712074

Fallback added for missing fileName in MultipartHTTPResponse

Resolved in Pega Version 8.7.2

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-213808 · Issue 710299

Stability enhancement to improve platform reliability and resiliency

Resolved in Pega Version 8.7.2

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-216261 · Issue 714413

Cases processed during archiving

Resolved in Pega Version 8.7.2

Cases were not being properly processed during archiving. This was traced to a missing pxObjClass in the clipboard page when the work index was being deleted, and has been resolved by adding pxObjClass to the clipboard page before sending the request for deletion.

INC-216313 · Issue 713525

Server push DSS name corrected

Resolved in Pega Version 8.7.2

Server push was not working. This was traced to an error in the specified name in the DSS, and has been resolved by modifying "prconfig/server-push/websocket/max_text_size/default" to the correct "prconfig/server-push/websocket/max-text-size/default".

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