INC-198571 · Issue 708633
SSO update
Resolved in Pega Version 8.7.2
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.
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.
INC-211184 · Issue 708499
Removed ORDER BY clause duplication when using MSSQL
Resolved in Pega Version 8.7.2
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 717432
Removed ORDER BY clause duplication when using MSSQL
Resolved in Pega Version 8.7.2
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.
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.
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-D75966 · Issue 537946
Check added so DT parameters passed when using anchor tag
Resolved in Pega Version 8.4.1
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.
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-D80539 · Issue 544795
Testcases are not available for 'access when' rules
Resolved in Pega Version 8.4.1
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.
INC-211018 · Issue 707526
Number control correct when IME is Japanese
Resolved in Pega Version 8.7.2
The Microsoft Windows Input Method Editor (IME) allows developers to enter complex characters in four different East Asian languages using the standard keyboard. When IME was in Japanese mode, entering a number resulted in the input happening twice with the result of an entry such as 12345 becoming 124512345. This has been resolved by updating the code to ensure there is no duplicate IME key