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-198571 · Issue 708633

SSO update

Resolved in Pega Version 8.7.2

In order to ensure shared SSO direct links are used as intended, an update has been made which will explicitly require re-authentication for each use of a direct link.

SR-D90779 · Issue 556916

Resolved error when using IHSummary as a predictor

Resolved in Pega Version 8.4.2

After configuring the adaptive model and implementing delayed learning with IHSummary as a predictor, the exception "dataflow.StageException" appeared when the strategy was executed as part of the dataflow run. This has been resolved by implementing a cache expiry of 5 minutes.

INC-211184 · Issue 708499

Removed ORDER BY clause duplication when using MSSQL

Resolved in Pega Version 8.7.2

After updating from Pega 8.4 to Pega 8.7, executing the query for the report definition generated the error "SQLServerException: Incorrect syntax near the keyword 'ORDER'." Investigation showed the ORDER BY clause was added to the Native SQL query from the standard dataflow background task and from the native SQL API as well when using an MSSQL database. This has been resolved by adding changes to restrict the order by clause if the SQL query has order by clause already for MSSQL.

INC-218491 · Issue 717432

Removed ORDER BY clause duplication when using MSSQL

Resolved in Pega Version 8.7.2

After updating from Pega 8.4 to Pega 8.7, executing the query for the report definition generated the error "SQLServerException: Incorrect syntax near the keyword 'ORDER'." Investigation showed the ORDER BY clause was added to the Native SQL query from the standard dataflow background task and from the native SQL API as well when using an MSSQL database. This has been resolved by adding changes to restrict the order by clause if the SQL query has order by clause already for MSSQL.

SR-D64566 · Issue 547515

Option added for redirect to SAML IDP on logout

Resolved in Pega Version 8.4.2

An enhancement has been added which provides a check box to choose to redirect to SAML IDP on logout from Pega.

SR-D64566 · Issue 547513

Option added for redirect to SAML IDP on logout

Resolved in Pega Version 8.3.3

An enhancement has been added which provides a check box to choose to redirect to SAML IDP on logout from Pega.

INC-125095 · Issue 560831

SAML authreqcontext duplicate key exception logging changed to debug

Resolved in Pega Version 8.4.2

As part of work done to improve the performance of the pr_data_saml_authreqcontext table during the SAML flow, the duplicate key exception handing was creating a large number of unique constraint log messages while saving sessionInfo to the database during SAML authentication if ADFS was used because the ADFS provider session Info is always blank. This has been resolved by changing the log statement in the duplicate key exception handling to debug.

SR-D95501 · Issue 557684

Updated jar supporting SAML login to work with JRE11

Resolved in Pega Version 8.4.2

SO authentication was failing with the exception "Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.ssl.TrustMaterial". That class was packaged with Pega via the not-yet-commons-ssl.jar which is no longer being developed and only works with JRE8. This has been resolved by updating the package to the new not-going-to-be-commons-ssl.jar which has been evaluated for all supported JRE versions.

INC-119754 · Issue 561523

Corrected 'when' rule context for GetCaseDetails

Resolved in Pega Version 8.4.2

The Pega REST API Get Method /cases{CaseID} failed if the Child Case was set with Manual instantiation using a 'when' rule. This was traced to the 'when' rule being resolved using @baseclass instead of the class of the case type, and has been resolved by updating the pzGetCaseDetails activity to evaluate the 'when' rule on the case page.

SR-D80539 · Issue 544793

Testcases are not available for 'access when' rules

Resolved in Pega Version 8.3.3

Attempting to create test cases for access when rules resulted in guardrail warnings about the need to create a test case. Because Test Cases are not available for the Access When rule type as per Pega expected behavior, the guardrail warnings are not valid and have been removed.

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