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.

SR-D46681 · Issue 514433

SnapStart supports SAML2 Authentication

Resolved in Pega Version 8.2.5

When using an HTTP Post to SnapStart into Pega using PRCustom style or PRAuth style SAML authentication, the login was looping back to the login request. Investigation showed that the Pega ACS was posting data properly back to the RelayState URL, however the login activity was not getting the SAMLResponse and simply sent a SAML Login Request again. This has been fixed by updating reqContextURI in case of SAML2 Authentication service so pyActivity=value will be passed.

SR-A101069 · Issue 270616

Fixed dropdown issues when using Google Chrome

Resolved in Pega Version 7.2.2

The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.

SR-A101069 · Issue 269981

Fixed dropdown issues when using Google Chrome

Resolved in Pega Version 7.2.2

The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.

SR-A101069 · Issue 270595

Fixed dropdown issues when using Google Chrome

Resolved in Pega Version 7.2.2

The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.

INC-144566 · Issue 600858

User lookup list correctly populated when using # tag

Resolved in Pega Version 8.4.4

When typing '#ANewTag @' in Pulse, the user lookup list was not shown. Using '#ExistingTag @' worked as expected. This was a missed use case in work done to improve the performance of pzJquerymentionsInput by restricting REST calls, and has been resolved.

INC-154855 · Issue 616002

Updated expression handling when not using client side validation

Resolved in Pega Version 8.4.4

After upgrade, a declare expression used to calculate the end date when creating a schedule case was not populating the result. This was traced to a missed use case for evaluating expressions when 'Enable client side validation' is unchecked, and has been resolved.

SR-D43141 · Issue 512434

Support added for iFrame Mashup resize when using SPA

Resolved in Pega Version 8.2.5

After upgrade, issues were seen with an iFrame holding a Mashup not resizing as expected. This was traced to the use of an SPA portal inside mashup, and has been resolved by explicitly invoking the doharnessResize API to set proper height on iframe when using SPA.

SR-A92057 · Issue 259453

OneTimeUse cache file generation disabled for SAML2

Resolved in Pega Version 7.2.2

Whenever SAML2 Token contained a "OneTimeUse" caching condition there were thousands of unwanted files generated. This caching has been disabled in the assertion validation code of SAMLv2ResponseProtocolValidator.java, so even if SAML2 token contains that OneTimeUse condition these files will not be generated.

INC-147245 · Issue 612867

Expand Pane icon responds to enter key when using JAWS

Resolved in Pega Version 8.4.4

In an Operator ID rule in Dev Studio, pressing the Enter key when focused on an Access Group expand icon caused the focus on the page to move to the top of the Contact Information frame (top left corner of the Frame). The only way to use the enter key to expand the pane without the refocus was to tab to the arrow icon and then tab a second time before pressing enter. This was traced to the expand caret icon being focussed twice due to the tabIndex for both the TD and SPAN elements holding the caret icon: TD had a focus element for accessibility of the grid, and SPAN had it for the expand pane accessibility. This has been resolved by adding a check condition before adding tabIndex to the first cell in the Grid.

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