INC-140224 · Issue 604005
Corrected SAML SSO error
Resolved in Pega Version 8.3.5
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-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-130299 · Issue 583924
Updated SSO operator authentication handling after passivation
Resolved in Pega Version 8.1.9
With SSO enabled and the pyAccessGroupsAdditional value list populated with the Mapping tab, attempting to access an expired session with an old cookie resulted in a stale thread exception while mapping value list attributes. This was due to using an AuthServicePage which was created by another session thread that had become stale for current session, and has been resolved by updating the code to call the authenticateoperator method on the authservicepage copy.
INC-144566 · Issue 600857
User lookup list correctly populated when using # tag
Resolved in Pega Version 8.3.5
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.
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.
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-137324 · Issue 584919
Corrected tabbing focus when modal flow has 'disable when'
Resolved in Pega Version 8.3.5
While tabbing through the modal dialog, focus moved to the background screen if there were custom flow action buttons that had a 'disable when' condition. This was caused by the last focusable element being a disabled element, and has been resolved by adding a disabled check in the getLastFocusableElement method that will determine whether element is disabled, and if so it will look for other elements as disabled elements can't be focused.
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.
INC-130677 · Issue 570040
When rule accepted in column header
Resolved in Pega Version 8.1.9
A grid was not rendering if it contained a 'when' rule on a column header. This was a missed use case and has been resolved.