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.
SR-D67150 · Issue 532023
Resolved attachments when using Mobile page message setting
Resolved in Pega Version 8.5
When using page-level error messages for a work object, trying to add an attachment to that work object resulted in an error and the attachment failed. This has been resolved by adding an error check in the pzAttachContentFile activity.
SR-D75966 · Issue 537945
Check added so DT parameters passed when using anchor tag
Resolved in Pega Version 8.5
When using a link control configured such that the value of the text in the link control refers to an anchor tag such as Text, clicking the link to launch a harness and call a DT with passed parameters was not working. Investigation showed that when the link had an anchor tag, pyDataTransformDynamicParams was not getting passed as query string parameter. In pega.desktop.showHarness function, there is a If condition which checks whether any "=" is present in preDataTransformName variable and if there is any, it does not add pyDataTransformDynamicParams. This was not an issue with anchor tag itself, but rather a generic issue: any value with "=" would behave in the same way. To resolve this, the pega.desktop.showHarness API has been updated to check against the proper value (pyDataTransform=) instead of just = to identify old modal parameters.
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.
SR-D88451 · Issue 550849
Testcases are not available for 'access when' rules
Resolved in Pega Version 8.5
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.
SR-D80539 · Issue 544794
Testcases are not available for 'access when' rules
Resolved in Pega Version 8.5
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.
SR-D90279 · Issue 554391
Data sync updated for use with DeferWrite
Resolved in Pega Version 8.5
After upgrade, attempting a data sync from the client mobile application worked for the first object submission, but the second object failed and stayed in the list. This was traced to finish assignments running back to back when deferWrite was enabled and svcPerformFlow failed to find the assignment. To resolve this, the assignmentHandle will be passed to the activity when calling the pzSetDeferWrite activity from FinishAssignmentActionProcessor.