SR-118125 · Issue 171188
Circumstance property value carried into dropdown options
Resolved in Pega Version 7.1.7
If a property of mode single value and type text was created with a defined local list of property values for the property, the value field was not automatically included in the dropdown options when attempting to use this property for circumstance/specialized flows. This was caused by an incorrect refresh section strategy used to determine when to reload the section for the circumstance by property, and has been corrected.
INC-139095 · Issue 596507
Portal loads for Simplified Chinese locale in IE
Resolved in Pega Version 8.5.2
When using IE, the portal would not load when using the Simplified Chinese locale. This was caused by Microsoft Internet Explorer rendering the locale as 'zh-CN-#Hans' instead of the expected 'zh-cn'. This has been resolved by adding a check to remove the "#" in the locale string to avoid a malformed URL.
INC-156826 · Issue 625439
Logic updated for adding new child/sibling to hierarchical paginated tree/grid
Resolved in Pega Version 8.5.3
When using a hierarchical table with pagination enabled, navigating to the last page and attempting to add a new child or sibling produced unexpected results. Navigating to the last row, selecting child, and clicking 'add sibling' caused a new row to be added. Adding a child caused the child elements to be added on top instead of at the bottom. This was a missed use case for adding a child/sibling when using a paginated tree/tree grid, and has been resolved.
INC-150172 · Issue 611775
Updated class handling for View field security
Resolved in Pega Version 8.5.3
When using a defined View which returned a page and its fields and used an inherited custom work party definition, trying to update the pyWorkParty(Customer) by calling the "post /assignments/{ID}/{actionID}" did not work as expected when Field Security was ON. This was traced to the field security relying on the design time page class information stored in the list/group property, and has been updated to resolve the view fields using actual class information from the work page.
INC-153281 · Issue 612785
Selectors updated for segmented radio buttons in Cosmos
Resolved in Pega Version 8.5.3
When using a Segmented format radio button in an application built on Cosmos, clicking the control caused the screen to flicker and the focus moved to the top of the screen. This behavior did not occur when performing the same action in a classic application built on UI Kit. This was due to a difference in positioning: in UI Kit, the input for the segmented radio button is positioned using an absolute position and the parent radioTable div uses a relative position, while in Cosmos the radioTable div is given a static position. This has been resolved.
INC-149823 · Issue 608352
DX API returns properly referenced icon class for embedded page
Resolved in Pega Version 8.5.2
When using the DX API to build an Angular JS UI, the response returned from the GET /cases/{ID}/actions/{actionID} api did not return the iconStyle for an icon class that uses a property reference when the flow is on an embedded page. This has been resolved by adding code to set the correct context for pzAPICreateJsonForModes and pzAPICreateJsonForField Rule-Utility-Function.
INC-142084 · Issue 599875
Support added for expression in strategy scorecards
Resolved in Pega Version 8.5.2
When invoking REST against a dataflow that had a strategy containing a scorecard that used an expression and the "Include model explanations option" was enabled in the Strategy configuration, the system failed with the error "PropertyValueInvalid .pxMaxScore Cannot cast the value (unknown) to double". This was traced to the Scorecard explanations failing during serialization when an expression was used, and has been corrected.
SR-111945 · Issue 157966
Closing Lucene search popup in Firefox corrected
Resolved in Pega Version 7.1.7
When using Firefox, it was not possible to close the popup box generated by a Lucene search unless a work object was selected first. This was caused by an error the the method used to access the document id, and has been corrected.
SR-118512 · Issue 175817
Improved error handling for iFrame XSS
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When using cross-site scripting with iFrame, attempts to use auto-complete did not populate data and an 'Access Denied' error was raised when keywords were entered for searching. While the system cannot access or modify iFrame content from another domain, the javascript for the autocomplete function has been modified to correctly handle any exceptions thrown while accessing iFrame from a different domain.
INC-137100 · Issue 604057
Added predictive text handler for Japanese on iOS
Resolved in Pega Version 8.5.2
The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.