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.

INC-140224 · Issue 604006

Corrected SAML SSO error

Resolved in Pega Version 8.4.4

After opening a case from the Pega-FCM portal or after logging in from SSO, closing the Pega window and opening it again resulted in the error "Unable to process the SAML WebSSO request : Violation of PRIMARY KEY constraint %27pr_data_saml_requestor_PK%27. Cannot insert duplicate key in object". This was a missed use case that happens only under the old SAML configuration, and has been resolved by removing a when condition that checks for stepstatus fail for the pySAMLwebSSOAuthentication activity.

INC-188162 · Issue 673507

RSA-PSS signature support added for for SAML SSO

Resolved in Pega Version 8.7

The XML security jars have been updated to incorporate RSA-PSS signature algorithm support.

INC-160485 · Issue 655297

Trailing "/" added to public links for SSO use

Resolved in Pega Version 8.7

Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it.

INC-178148 · Issue 660924

Handling added for SSO servlet name

Resolved in Pega Version 8.7

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

INC-188405 · Issue 673063

Handling added for SSO servlet name

Resolved in Pega Version 8.7

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

SR-133715 · Issue 204978

RTE <br> handling resolved when using pega:when = false

Resolved in Pega Version 7.2

Inconsistent behavior was seen when using rich text editor in paragraph rule if the pega:when was false. This was an issue with the handling of the
tags under this condition, and has been resolved.

SR-133715 · Issue 209655

RTE <br> handling resolved when using pega:when = false

Resolved in Pega Version 7.2

Inconsistent behavior was seen when using rich text editor in paragraph rule if the pega:when was false. This was an issue with the handling of the
tags under this condition, and has been resolved.

SR-A3803 · Issue 212217

Better handling for menus when using JAWS

Resolved in Pega Version 7.2

When accessibility was invoked, the Navigation menu did not indicate arrow up/down options in links with showmenu role='link' generated on them, and JAWS was not reading out that it was a link with a menu. This was an unintended side-effect of updates to avoid reading out a URL in a label/text, and corrections have been made to support accessibility so that navigational menus are read out more intuitively with JAWS.

SR-A8595 · Issue 218942

Security updated for SAML Rule keystores

Resolved in Pega Version 7.2

Password encryption has been updated for the Keystores records used by SAML Rule forms for signing and decryption in the auth service rule data.

SR-A7590 · Issue 216110

Corrected parameter page used when Flowproblems restarts

Resolved in Pega Version 7.2

Restarting the problem flow was not taking the mandatory parameters defined in the flow, instead generating the error "Required parameter Parameter_name." To correct this, the flow method body has been modified to populate the parameter page from the pyFlowParameters page before checking for mandatory parameters.

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