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-128883 · Issue 195834
Fixed button contrast when using accessibility
Resolved in Pega Version 7.1.8
The "Select Values" button in the dialog to edit report filter had a low contrast ratio when accessibility was enabled. This was caused by the unintentional application of the repeat layout CSS to the button, and has been fixed.
SR-130224 · Issue 200002
Fixed class pickup when Ticket Urgency is used as reference
Resolved in Pega Version 7.1.8
It was not possible to convert a summary report to a list report if the report had Ticket.Urgency as a reference and Ticket was a single page pointing to data class type property in the work class. This was traced to the drill down picking up the Urgency property from the work class, and has been resolved.
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-119772 · Issue 175593
Menu rendering corrected for Attachment Menu controls when using JAWS
Resolved in Pega Version 7.1.8
Previously, the 'add menu' button in the Attachment Menu controls did not respond to the spacebar or enter key if JAWS was active. This was due to a rendering issue with the work flow menu options and has been resolved.
SR-C67397 · Issue 421638
Added check for missing rule data when using abstract class in CSS
Resolved in Pega Version 8.2.1
Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page.
SR-126156 · Issue 190077
Random ID generation changed to use OpenSAML
Resolved in Pega Version 7.1.8
In certain cases, SSO setup with SAML 2.0 failed with the message "Unable to process the SAML WebSSO request: Unable to process SAML2 Authentication". The error was due to the generated ID being sent with a "+" character in it which could not be handled smoothly. To avoid this issue, the system has been changed to use the OpenSAML API instead of using UUID when generating random IDs for all types of WebSSO requests.
SR-C80372 · Issue 425075
Oniine help files updated to more completely reflect SAML Authentication Rule Form fields
Resolved in Pega Version 8.2.1
The online help files have been updated to reflect that the SAML Authentication Rule form has various fields including Entity Identification, Login Location, Logout protocol binding, and Artifact Resolution Service Location that support GRS syntax (=D_myDataPage). When configuring SAML it is also required to update WebSSO Service Package to point to the Access Group as the Application Access Group. https://community.pega.com/sites/default/files/help_v74/procomhelpmain.htm#concepts/concepts2/globalresourcesettingfields.htm
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-145902 · Issue 604196
Corrected tab alignment with when expression
Resolved in Pega Version 8.3.5
The tab layout group was not aligned properly in the Case Worker portal when using the Tab Layout Group with Enable stretch for the tabs checked and a when expression on one of the tabs. This was traced to the updateStretchTabWidths API not being triggered in the correct context due to a condition resolving as false. This has been corrected by adding an additional condition to enable the correct resolution and context.