INC-155813 · Issue 629504
SAML SSO redirects to correct URL when application and authentication aliases match
Resolved in Pega Version 8.4.5
Whenever there was a match in the authentication service alias and the application alias, the application alias was replaced with empty after logoff instead of making the authentication service alias empty. For example, given an authentication service with the alias XYZ ("login with XYZ" alias option) and an application name XYZMyOps, the application alias was being changed from XYZMyOps to appMyOps after logoff. As a result, a blue screen error resulted when clicking on button "login with XYZ" again because it redirected to appMyOps, which didn't exist. This has been resolved by removing authservicealias and modifying AuthServiceAliasHelper.adjustPathIfAuthServiceAliasPresent() to change the method for calculating the pathinfo to string tokenizing.
SR-D46681 · Issue 514435
SnapStart supports SAML2 Authentication
Resolved in Pega Version 8.1.8
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.
INC-170423 · Issue 648982
Added catch for SAML WebSSO duplicate key exception
Resolved in Pega Version 8.4.5
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. Cannot insert duplicate key in object." This has been resolved by updating the session index handling and adding a catch for the duplicate key exception.
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-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.
INC-146837 · Issue 602673
PerformCriteria contains CurUserHasRequiredSkills 'when' rule
Resolved in Pega Version 8.1.9
A customer version of the PerformCriteria data transform was generating a validation error due to a qualified statement that resulted in a null result. This has been resolved by updating the PerformCriteria DT to include the CurUserHasRequiredSkills 'when' rule.
INC-143545 · Issue 600711
Support for 'when' action evaluated in runtime
Resolved in Pega Version 8.1.9
A 'when' rule was not evaluating properly on enabling "Optimized code" and "Personalize table" options for table/grid. This has been resolved by adding support for a 'when' action in a templated grid.
INC-163452 · Issue 631831
Validation correctly triggered when skipping flows
Resolved in Pega Version 8.4.5
When using a screen flow which allowed users to navigate the flow freely, validation was not triggered on submission. In addition the server or client side validation was being cleared when the case used optimistic locking. Investigation showed that pzShowConflicts was called for optimistic locking on FinishAssignment, which was clearing off the messages and allowing the flow submission. To correct this, a check has been added to pzShowConflicts to check for defer errors in screenflow while clearing page messages.
INC-164311 · Issue 635784
Correct datetime target property used
Resolved in Pega Version 8.4.5
When using a declare expression for a datetime property to get its value from another datetime property, attempting to change the source datetime later resulted in the error "28-mar-2021 is not a valid date/time value". This occurred when the source datetime property had display readonly formatting, and was traced to the formatted value being sent in the callGetTargets API instead of the selected date value, which caused the function to be returned as empty because there was no target property in the same page before submission. To correct this, a check has been added which will get the value from data-value instead of element.value and will skip callGettragets if the target is empty.
INC-175630 · Issue 653865
Application selections only announced when visible
Resolved in Pega Version 8.4.5
The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.