SR-C74648 · Issue 422905
Autocomplete arrow placement corrected in Right to left local mode
Resolved in Pega Version 8.2.1
When using the Autocomplete control, the blue arrow was seen to have an incorrect placement/orientation in RTL mode. This was traced to the autocomplete background-image in RTL mode being the same as that for LTR, and has been resolved by adding specific background-image for RTL.
INC-182572 · Issue 663557
Support added for multiple host proxy architecture
Resolved in Pega Version 8.7
When using an architecture where certain types of users were sent through multiple proxy servers to get the Pega Cloud instance, an exception was generated at the point of accessing the environment. This was traced to the use of Apache 2.4 with mod_proxy. As the request passed through each proxy, the x-forwarded-host header had values appended to it by mod_proxy which resulted in the error "com.pega.pegarules.pub.context.PRSecurityException: Multiple host names in header X-forwarded-Host". This has been resolved by updating the code to support using a multiple host proxy configuration.
SR-C76417 · Issue 430546
Check added for reference function in DB2 join
Resolved in Pega Version 8.2.1
In DB2, when a sub-report column contained a function that was used for a join condition in the main report, an invalid filter property error was generated while saving. This was traced to the edit validate rule checking for the data type of both of the properties used in the join, and has been resolved by adding a check to see if the join operand is of function 'reference'; if so, the system will resolve the function, check for data type property, and set it.
INC-169116 · Issue 654256
Correct time zone chosen for fr_Fr appointment functionq
Resolved in Pega Version 8.7
When using the "fr_Fr" location and and "Europe/Paris" time zone for appointments, a null pointer exception was seen related to the function getStartOrEndDateTime. Investigation showed that the incorrect time zone was being picked from the fr_FR.xml file when parsing the date. To resolve this, 4 letter time zone codes have been moved above the 3 letter time zone codes.
INC-163544 · Issue 639301
Accessibility corrected for Cosmos user portal left navigation panel
Resolved in Pega Version 8.7
It was not possible to see the focused control label in the left pane of the Cosmos user portal because it was not expanding when its control received focus from tabbing. Investigation showed the class acting as a polyfill for :focus-within was applied only on the observed element when using Microsoft Explorer 11, and this has been resolved by updating the CSS selectors and ensuring the class is applied to every parent element down the DOM tree.
INC-183712 · Issue 674132
IndexOf updated to remove extra bracket
Resolved in Pega Version 8.7
When trying to open a section rule, content was not loading if values were derived using a report with column containing a function. This occurred when the section rule included a table referencing the report where one of the section table cells had its Property value set to the function. To resolve this, indexof has been updated to not include closing > as the HTML returned from the server now includes an attribute on that tag.
SR-B41316 · Issue 306255
Resolved missed cases in the WO case tree
Resolved in Pega Version 7.3.1
Sometimes several cases were missed in the case tree, shown in the right side of an opened WO. Access was not available for the corresponding WO and assignments. The root cause was a WHEN condition in WORK-COVER- PZLOADNESTEDCASESFORCLASS property "local.ProcessedItemKeys" containing numbers of processed WOs separated by a space, for example, "KPI-101 KPI-72 KPI-52". The WHEN condition checks for presence using "contains", leading "KPI-10" to be ignored and not displayed in cases where "KPI-101" already presented. To correct this, the system will consider the delimiter "\t" while checking the WHEN condition.
SR-B41316 · Issue 306260
Resolved missed cases in the WO case tree
Resolved in Pega Version 7.3.1
Sometimes several cases were missed in the case tree, shown in the right side of an opened WO. Access was not available for the corresponding WO and assignments. The root cause was a WHEN condition in WORK-COVER- PZLOADNESTEDCASESFORCLASS property "local.ProcessedItemKeys" containing numbers of processed WOs separated by a space, for example, "KPI-101 KPI-72 KPI-52". The WHEN condition checks for presence using "contains", leading "KPI-10" to be ignored and not displayed in cases where "KPI-101" already presented. To correct this, the system will consider the delimiter "\t" while checking the WHEN condition.
SR-B56485 · Issue 312961
Mashup gadget cookie requests consolidated in Safari
Resolved in Pega Version 7.3.1
In order to resolve an issue when using Safari where Pega was displaying a message to allow cookies for every Mashup gadget, the isCookieConsentRequired method in PegaCompositeGadgetMgr.js has been updated to check if the host URL and gadget URL are the same to avoid duplicate messages.
SR-B43999 · Issue 310047
Corrected accessibility for complex dynamic layout headers
Resolved in Pega Version 7.3.1
JAWS was not able to interact with complex nested dynamic layout structure when the innermost dynamic layout had a Header / "Title" set. This was traced to the generation of empty tables in the Dynamic layouts related to the use of the Show container Icons checkbox, and has been fixed.