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-126490 · Issue 190168

Disabled unneeded PEGA0050 alerts

Resolved in Pega Version 7.1.8

PEGA0050 alerts were triggered when a clipboard page list was copied to another list. In general these copies happened when lightweight page lists are involved. In Pega 7, lightweight lists have been enhanced and these copies are not required in most of the cases. Because it is no longer needed, the "alerts/virtuallists/copy" setting has been changed to false to disable the alerts

SR-126545 · Issue 189937

Added remote case handling for password protected implementation applications

Resolved in Pega Version 7.1.8

There was a problem creating an implementation application in Application Express if the built-on application was password protected and the current logged-in application was also password protected, and the cases from built-on have remote case types. This was caused by validation issues, and has been corrected by modifying 'CreateObjectByPage' to pass the parameter 'SkipAddRemote' while calling save activity as true. Save will use this activity to skip current validation through 'ManageRemoteWorkTypesInApplication'.

SR-126587 · Issue 191010

Workbasket name updated in Case Manager portal

Resolved in Pega Version 7.1.8

When CaseManager portal was launched and any particular WorkBasket selected, the text "WORK IN XXXXX WORKBASKET" was shown. XXXXX was the WorkBasket name, which was being picked from RuleName(Identifier) instead of ShortDescription. This was unexpected, and has been changed.

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-128118 · Issue 191010

Workbasket name updated in Case Manager portal

Resolved in Pega Version 7.1.8

When CaseManager portal was launched and any particular WorkBasket selected, the text "WORK IN XXXXX WORKBASKET" was shown. XXXXX was the WorkBasket name, which was being picked from RuleName(Identifier) instead of ShortDescription. This was unexpected, and has been changed.

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.

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