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.

SR-119601 · Issue 176925

ParseXmlObjectWrapperAssembler updated to handle embedded pages

Resolved in Pega Version 7.1.8

Parse XML rule compilation was failing if the Pages and Classes tab of Parse XML rule included an embedded page. This was traced to an assembler issue and ParseXmlObjectWrapperAssembler has been updated to resolve compilation issues in case of named pages.

SR-119648 · Issue 177559

JavaMAIL version updated for GMail compatibility

Resolved in Pega Version 7.1.8

A third-party product integrated with PRPC was causing mail and attachments to not appear properly when using Gmail due to an incompatibility with Gmail's interpretation of IMAP. To correct this, the provided JavaMAIL version has been updated from 1.4.1 to 1.5.2.

SR-119978 · Issue 184032

Corrected handling for properties in XML rule

Resolved in Pega Version 7.1.8

When using properties mapped on the root element of an XML SOAP rule, the attributes were mapped properly but the element value was not. In a related error, after giving ParseXML rule invocation values for Type Substitution for Parse XML, the XML was not mapped to the clipboard for the type substituted elements. There was a workaround of using DSS 'switchtooldassembler', but this has been fixed by updating parsexmlsaxrulewrapper.

SR-120224 · Issue 178688

Potential vulnerability closed in XML stream generation

Resolved in Pega Version 7.1.8

A potential security issue was found with the XML stream generation and runtime, and has been corrected.

SR-120329 · Issue 178133

Assembler compatibility issue resolved

Resolved in Pega Version 7.1.8

After upgrade, web services that modify the Header were failing due to a compatibility issue with the default assembler. While there was a workaround of giving the value of 'true' to the dynamic system settings 'Owning ruleset: Pega-IntegrationEngine' and 'Setting purpose: switchtooldassembler', this has been resolved.

SR-120454 · Issue 188836

Fixed error handling for MDB listener

Resolved in Pega Version 7.1.8

JMS MDB listener was failing and throwing 'NoClassDefFound' errors in the PegaRULES log file. The issue was found to be the error reporting in one of the integration methods, and has been fixed by modifying the ServiceAPI.generateErrorMessage such that if LogHelper cannot be used, an error is reported in the system error file and the listener continues.

SR-120525 · Issue 186509

Added handling for special characters in PDF Eforms

Resolved in Pega Version 7.1.8

PRPC uses a third-party library 'iText' to read and write PDF 'Eform' documents. It was found in some cases that if the input document contains fields ("Acrofields") that contain special characters (in particular the '#' hash/pound symbol) and/or accented characters, then the iText library would throw an error. To eliminate this, a check of the Field Name has been added to ensure it has a value before doing anything with it. If it is empty, that will be logged. As a workaround, it was found that by editing the input PDF file (using an appropriate third-party editor/generator) and ensuring that no field names ("Acrofields") contained special characters or accented characters, the iText library (and then subsequently the PRPC activity "GenerateEform") was able to process the input file and correctly produce the 'filled-in' output PDF 'EForm'.

SR-120596 · Issue 183801

Resolved mapping issue for SOAP-connect with multirefs

Resolved in Pega Version 7.1.8

After upgrade, mapping the soap-connect response to page in activity was not working as expected. This was an issue with a Parse-XML rule, and has been corrected with added support for multirefs and SOAP arrays with multirefs.

SR-120701 · Issue 179702

Email listener error handling improved

Resolved in Pega Version 7.1.8

When an email arrived with a zero byte attachment, the email listener was failing to generate a work object. An error was seen in the log, and the listener marked the email as seen even though no WO was created. This has been fixed by suppressing the IOException that arises while processing a zero-size INLINE attachment, allowing the rest of the email message to be processed. An exception will be logged, but the attachment that caused the issue will not be added to the work object.

SR-120730 · Issue 178759

Fixed FCM access for remote work item attachments

Resolved in Pega Version 7.1.8

When using FCM to access remote work item via find by ID, attempting to open the history / attachments popup generated a green tick (success but no content) on the first attempt and the error "Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'HISTORYANDATTACHMENTS' that applies to '@baseclass'" on subsequent attempts. "the operation completed successfully, but returned no content". The issue only happened when first logging on and searching for a work item and did not occur if the tab was closed and the same work item reopened. This was caused by the prgateway sending an HTTP request where the Pega thread name in the URL was stripped of a slash, triggering the creation of a brand new Pega thread where expected pages were missing. To resolve this, the code has been updated to correctly maintain slashes and add them if necessary.

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