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.

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-119762 · Issue 176867

Case Manager search accessibility enhancement

Resolved in Pega Version 7.1.8

The 'Search' field in CaseManager has been enhanced to be more informative for end users to perform tasks and includes information that the follow-on menu holds options for 'search by' criteria. In addition, the 'Landmark Menu' has been provided with a search field for quick navigation and accessibility.

SR-119780 · Issue 175524

Added accessibility for CalendarViewGadget's month switch

Resolved in Pega Version 7.1.8

The CalendarViewGadget's month switch arrow buttons/icons have been updated to support navigation with the keyboard and respond to the TAB key, allowing full access to this function within the accessibility framework.

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-120381 · Issue 179868

TopLevelClass updated to accept a hyphen in the name

Resolved in Pega Version 7.1.8

Previously, the new application wizard Top-Level class did not support the use of a dash between two ruleset classes. An enhancement has been added to allow this format.

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-120518 · Issue 180099

Corrected error handing on"Post Action on Click Away"

Resolved in Pega Version 7.1.8

When an assignment in a screen flow was configured to use the "Post Action on Click Away" setting, it was not possible to go back if there were validation messages on the screen. Without the "Post Action on Click Away" setting, the click back worked and the validation message was cleared by the jumpToTask activity. This work flow issue has been fixed by clearing the page error messages before calling performflowaction.

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