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-126530 · Issue 193829

Enhanced error handling for exceptions generated by import

Resolved in Pega Version 7.1.8

After upgrading to a single schema on Oracle 11.2 database, the system started up showed the login page, but once logged in a blank Screen/UI would be displayed and errors were logged indicating "Failed to resolve rule file". The rule file varies depending on the content source. This issue was caused by exceptions not being handled properly by import, and has been resolved by modifying the runWithRequester method (importImpl.java) to check for Exception as a return object object from the method invocation, and propagating the exception if one is returned.

SR-126719 · Issue 177348

Added fallback keyinfo handling

Resolved in Pega Version 7.1.8

When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.

SR-126719 · Issue 178793

Added fallback keyinfo handling

Resolved in Pega Version 7.1.8

When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.

SR-131723 · Issue 199975

Resolved RD header alignment

Resolved in Pega Version 7.1.8

When given a requirement to have a fixed size of 250 rows in a Report Definition (RD), selecting the "Do not scroll header" option caused the alignment of the header to be lost. This has been corrected.

SR-131723 · Issue 200028

Resolved RD header alignment

Resolved in Pega Version 7.1.8

When given a requirement to have a fixed size of 250 rows in a Report Definition (RD), selecting the "Do not scroll header" option caused the alignment of the header to be lost. This has been corrected.

SR-128213 · Issue 196729

Summary View handling added for property name missing dot

Resolved in Pega Version 7.1.8

In Summary View, it was not possible to add an embedded property for the drill down if the property name was missing a leading dot. A null check has been added to eliminate the NPE and handle this issue.

SR-128213 · Issue 195827

Summary View handling added for property name missing dot

Resolved in Pega Version 7.1.8

In Summary View, it was not possible to add an embedded property for the drill down if the property name was missing a leading dot. A null check has been added to eliminate the NPE and handle this issue.

SR-128423 · Issue 193544

RD filter caption localized

Resolved in Pega Version 7.1.8

In report definition, expanding the filter link showed the caption of the filter icon was not localized. This has been corrected by creating a new control and applying it to pyFilterLabel in pzEditSingleFilter.

SR-128423 · Issue 194206

RD filter caption localized

Resolved in Pega Version 7.1.8

In report definition, expanding the filter link showed the caption of the filter icon was not localized. This has been corrected by creating a new control and applying it to pyFilterLabel in pzEditSingleFilter.

SR-131985 · Issue 201549

Sorting now working with filtering and pagination for RD

Resolved in Pega Version 7.1.8

Using filtering and pagination on Report Definition and then sorting on one of the subpages caused the error "no results found". This was an issue with the page index not being reset to 1 on apply of modal dialogue, and has been corrected.

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