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-B4391 · Issue 275319

GenerateGridHTML updated for JAWS version compatibility

Resolved in Pega Version 7.3

An update to the JAWS program caused it to no longer recognize some Pega grids as tables due to the use of role=presentation, and the table name was not associated with the layout header title leading to the tables not being labeled accordingly. To correct this, the GenerateGridHTML now has an added summary attribute in the ".gridTable".

SR-B43927 · Issue 300881

Net commons SSL JAR updated

Resolved in Pega Version 7.3

The net commons SSL JAR has been updated to the latest version.

SR-B43950 · Issue 300643

SAML SessionInfo cleanup enhanced

Resolved in Pega Version 7.3

The following SAML issues have been corrected: 1) when IDP logout URL was empty, SAMLSingleLogOff activity generated an exception; 2) the SAML Session info record was not deleted during logout process even when given a valid IDP logout URL; 3) the SAML session info record was not deleted for both SP and IDP initiated logouts.

SR-B43950 · Issue 301551

SAML SessionInfo cleanup enhanced

Resolved in Pega Version 7.3

The following SAML issues have been corrected: 1) when IDP logout URL was empty, SAMLSingleLogOff activity generated an exception; 2) the SAML Session info record was not deleted during logout process even when given a valid IDP logout URL; 3) the SAML session info record was not deleted for both SP and IDP initiated logouts.

SR-B44001 · Issue 302395

Bulk Action filter handles rule withdrawn from landing page

Resolved in Pega Version 7.3

If a property was withdrawn in the Bulk Actions landing page, the other page properties no longer appeared in the Filter Property list. This was due to the getImmutableTerminalPropertyInfo function causing an exception whenever the rule availability was empty. To resolve this, the system will check the availability of the property rules in the "Rule-Obj-Property.LookupList" activity's 3rd step before processing/adding the embedded properties.

SR-B44146 · Issue 300050

Resolved error in adding Association's Page Property in report browser

Resolved in Pega Version 7.3

Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.

SR-B44199 · Issue 300058

Fixed Access Control Policy in Assign- classes

Resolved in Pega Version 7.3

An error was generated when attempting to create an Access Control Policy in Assign- classes. This was due to a missing use-case, and has been corrected.

SR-B44199 · Issue 299984

Fixed Access Control Policy in Assign- classes

Resolved in Pega Version 7.3

An error was generated when attempting to create an Access Control Policy in Assign- classes. This was due to a missing use-case, and has been corrected.

SR-B44199 · Issue 297134

Fixed Access Control Policy in Assign- classes

Resolved in Pega Version 7.3

An error was generated when attempting to create an Access Control Policy in Assign- classes. This was due to a missing use-case, and has been corrected.

SR-B44278 · Issue 302830

MT guide updated for rules blocking/restriction

Resolved in Pega Version 7.3

The MultiTenant guide has been updated to clarify what causes rules to be blocked or restricted and the possible consequences of unrestricting rules.

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