INC-198571 · Issue 708634
SSO update
Resolved in Pega Version 8.8
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.
INC-222404 · Issue 727870
AccessToken can be used for both OIDC SSO and Connect-REST
Resolved in Pega Version 8.8
When trying to specify the AuthenticationProfile with grant_type ‘authorization_code’ in the Connect-REST rule, the AccessToken was not being retrieved, and the error "services.OutboundMappingException: Caught Exception while creating OAuth2 client, Caused by: PRRuntimeException: Unable to obtain access token for client details in authentication profile configured for connector" was generated. The usage case desired is to use the same token for both OIDC SSO and Connect-REST. This worked when the scope was the same, but the key was constructed with a space between the scope and the operator ID while saving the token to the cache. The constructed key did not have this space when fetching the token during Connect-REST. To support the desired use, logic has been added to make the appropriate trim for scope in cache key generation in oauth2clientimpl.
INC-223222 · Issue 723635
Corrected apiContext when using bulkActions
Resolved in Pega Version 8.8
Row selections in the multi-selection table were intermittently not working after opening a table with bulk actions enabled. Investigation showed that opening a table with bulkActions enabled and then navigating to a table where bulk actions are not available but multi-select is enabled led to functions like setSelectedRows and getSelectedRows still being available in apiContext. This has been resolved by correcting apiContext when bulkActions is enabled.
INC-215062 · Issue 722018
Removed ORDER BY clause duplication when using MSSQL
Resolved in Pega Version 8.8
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 717433
Removed ORDER BY clause duplication when using MSSQL
Resolved in Pega Version 8.8
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-170423 · Issue 648984
Added catch for SAML WebSSO duplicate key exception
Resolved in Pega Version 8.5.4
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-162434 · Issue 640052
LookUpList correctly executes during SSO login with model operator
Resolved in Pega Version 8.5.4
After configuring SSO to create operators on fly using a model operator, a new user logging in for the very first time had their operator ID created using the model operator, but after upgrade new users logging in to the system received the error "Only authenticated client may start this activity: RULE-OBJ-ACTIVITY @BASECLASS LOOKUPLIST". This was due to the methods used for additional security on the activity @baseclass LookUpList which allows it to only be run by authenticated users, and has been resolved.
INC-155878 · Issue 645364
Class list updated when using ActivateDocument in portal navigation
Resolved in Pega Version 8.5.4
Global search worked the first time it was used, but failed after another case was opened from the dashboard or there was a click on any landing page home, dashboard, or space. Investigation showed this was caused by the pySearchText being blank in the clipboard, which was traced to a harness context issue related to pega.desktop.activateDocument being used in pzPortalNavigation on DynamicLayout with Application Logo and Application label. To resolve this, an update has been made that will update the class list with the proper one when the data-harness-id is set.
INC-161409 · Issue 632725
Added handling for checkbox group to use form tag when field tag is not available
Resolved in Pega Version 8.5.4
After configuring the Checkbox group component from the UI gallery in one of the sections in an application built on Theme-Cosmos, the configuration worked as expected when creating a new case type, but opening this WorkObject from the Associated cases section on the child case caused behavior issues including being able to select select multiple options instead of a single radio button. Investigation showed this happened when navigating through the work flow under the Perform Harness, but worked as expected when navigating through the Review Harness. This has been resolved by modifying the selectors to target form tag if the fieldset tag is not available.
INC-168837 · Issue 646973
CSRF token updated for use with OKTA login
Resolved in Pega Version 8.5.4
An issue seen while connecting via OKTA has been resolved by updating the CSRF token validation for use with IDP initiated SSO login.