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-211599 · Issue 708544

Data page definition reload made more robust

Resolved in Pega Version 8.8

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 714060

Removed extra space in Malaysian locale

Resolved in Pega Version 8.8

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

INC-211977 · Issue 713460

Handling added for large BIX Postgres data sets

Resolved in Pega Version 8.8

BIX extracts were causing timeouts or JVM out of memory errors. This was traced to the Postgres JDBC driver ignoring fetch size in auto-commit transaction mode, which led to everything being loaded into memory at once. To resolve this, changes have been added to support fetch size for large results when using PostgreSQL database for BIX Extraction.

INC-212251 · Issue 720198

Editable data page properly refreshes after interaction

Resolved in Pega Version 8.8

A data page using editable mode was adhering to the "Reload once per interaction" option used for readonly mode. This led to issues such as tables not refreshing after sorting or applying filters. To resolve this, refreshReloadInteraction has been updated to false when mode is not readonly.

INC-212433 · Issue 724512

Clarified SLA calendar error message

Resolved in Pega Version 8.8

If a calculated SLA date is out of calendar end date range, the error "Perhaps the business calendar of year XXXX is missing" is generated. When the provided start date is not the business day and the SLA was calculated by using a custom activity using addTime, isBusinessDay and pxGetSpecifiedTimeOnDate function, this message showed the current year calendar. When checked in the tracer the exception was thrown with the correct year calendar, but when the exception was written as an alert the message was changed and provided the misleading error on the screen. This has been resolved by addressing the misleading error message.

INC-212729 · Issue 699682

ClusterAndDBCleaner updated to with with Oracle query limits

Resolved in Pega Version 8.8

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 711003

ADLS/File listener support added

Resolved in Pega Version 8.8

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

INC-213124 · Issue 724632

AWS file type added for S3 uploads

Resolved in Pega Version 8.8

The correct content type was not getting set when uploading images to S3 using the "pxPublishArtifacts" activity. This has been resolved by adding the content type for AWS files while uploading to S3.

INC-213308 · Issue 712076

Fallback added for missing fileName in MultipartHTTPResponse

Resolved in Pega Version 8.8

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-214451 · Issue 734925

Rest connector passes RequestAttachmentPage to child requestor

Resolved in Pega Version 8.8

While invoking the Rest Connect from a data page, the error "InboundMappingException: Exception occurred while mapping incoming response" was generated. Requests with "Content-type:multipart/form-data" require "pyRequestAttachmentPage" or "pyResponseAttachmentPage" to be populated with correct values. When Rest-Connector was executed in parallel, those pages were not copied to the child requestor and the rest call executed from the child requestor did not have correct header and body. To resolve this, MethodConnect.java has been updated to correctly pass pyRequestAttachmentPage to the child requestor.

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