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-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.

INC-215572 · Issue 712389

SOAP integrations documentation updated

Resolved in Pega Version 8.8

The documentation for dynamic system settings used to modify SOAP integrations has been updated to list all available DSS for SOAP connectors and services, with a clear purpose for each setting. https://docs.pega.com/data-management-and-integration/87/dynamic-system-settings-soap-integrations

INC-215671 · Issue 719074

Support added for special characters in XML stream rules

Resolved in Pega Version 8.8

When using an XML Stream rule, node values were encoded for a broader set of characters than was required to create properly formed XML. Special characters were converted to ASCII characters when setting the XML to a property with Property-Set-XML. When the mode of the element was changed from Standard to Literal XML, the special character was retained but the element tag itself was missing. This has been resolved by adding a new "XML" encoding format in StreamBuilder. In ResponseTag.appendUnformattedValue(), use the XML mode when resolving to "NORMAL" format and the JSP base class is "Rule-Obj-XML". In StreamBuilderTools, the system will not encode '+' symbols when in XML mode.

INC-215953 · Issue 719060

Added index check to avoid unnecessary error message

Resolved in Pega Version 8.8

After updating from Pega 8.3 to Pega 8.6, the post upgrade task "Upgrade application schema" unexpectedly listed that the PegaDATA "pr_history_idx3" entity was missing under the "Missing Pega Platform shipped schema" section. This was traced to a change in Pega 8.4 which renamed pr_history_data_idx1 to pr_history_data_idx3, causing the error due to normal operation skipping the creation of an index with the same keys. To resolve this, the update logic has been modified such that before dropping an index, a check will be performed to see if there are any other indexes in pegarules-master that are not marked for deletion but have the same composite key as the index to be dropped. If there is a matching index, the index will not be dropped and the error will not be seen.

INC-216261 · Issue 714414

Cases processed during archiving

Resolved in Pega Version 8.8

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 713526

Server push DSS name corrected

Resolved in Pega Version 8.8

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".

INC-216380 · Issue 722700

Update impact for Pega Call

Resolved in Pega Version 8.8

Log4j-1.2.14.jar and Log4j-1.2.17.jar have been removed to address the security concerns with these versions, and logger jars have been upgraded to 12.7.2 version (from 12.7.1 version) to make Pega Call compatible. This change will impact Pega Call customer environments due to Avaya or Genesys, which are part of Pega Call, having an internal dependency on Log4j1.x version jars. As a result, the SDK logging for Avaya or Genesys will not be available in the 8.8 release unless the Log4j-1.x jar files are reimported locally. Please refer to https://docs.pega.com/pega-call-release-notes/87/changes-update-impact

INC-216381 · Issue 716614

BigDecimal handling updated for @ sum function

Resolved in Pega Version 8.8

The @ sum function was not behaving correctly. This was traced to the java code in the 'sum--(ClipboardPropertyCollection)' function which was not properly converting the double to Bigdecimal for some of the inputs like 500, 500, 600.11. This has been resolved by modifying the function to convert input properties to BigDecimal, add BigDecimal values, and return the result.

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