INC-139739 · Issue 598902
Cross-Site Scripting protection update
Resolved in Pega Version 8.5.3
Cross-Site Scripting protections have been updated for labels.
INC-141302 · Issue 614994
UI automation script documentation update
Resolved in Pega Version 8.5.3
To provide a more consistent experience, explanatory comments in the code for UI automation scripts have been removed.
INC-143363 · Issue 604363
Added handling for maintaining on-change event descriptor
Resolved in Pega Version 8.5.3
The multiselect control was not reliably posting the values to the configured page list property if the change actions were performed very quickly. Multiselect calls triggerCustomEvents, which handles the schedule for an event: when change actions are entered in a paced way they are not added to a queue, but when performing on-change very fast events are added to a queue and processed later. In this case, the queuing caused the correct event descriptor to be lost because the original event flows were not followed. This has been resolved by adding custom handling which will maintain the event descriptor.
INC-144522 · Issue 612323
Portal primarythread copied to workprocessing thread to establish proper class
Resolved in Pega Version 8.5.3
Attempting to add a new item/row in a table configured in a modal dialog in the home page of the Cosmos portal was not working, and the error "Section 'TestSection' execution error on page 'pyWorkPage' of class 'CosmosApp-Work-TestCaseType'. : For input string: "" appeared. This was a missed use case for pyPortalHarness, and was caused by the primarypage not getting copied to the workprocessing thread which led to some actions failing as classless. This has been resolved.
INC-144572 · Issue 600757
Corrected mobile tab layout highlighting
Resolved in Pega Version 8.5.3
When switching between three tabs in a layout group (Other � Mobile Tabs) in a section, the highlight was appearing on the active tab and the inactive tabs. This has been resolved by updating the CSS generation to not consider hover styles for touchable devices.
INC-144709 · Issue 608798
Removed unnecessary decoding from GetDropdownOptions
Resolved in Pega Version 8.5.3
When using a dropdown sourced by a data page with parameters in the section, passing multiple values as the parameters of the data page resulted in the error "pzGetDropdownOptions:Invalid JSON Stream for data page params" and the parameter values were not resolving at runtime. This was traced to unnecessary decoding in the process, and has been resolved.
INC-144778 · Issue 619615
Performance improvements for Ajax tab switching
Resolved in Pega Version 8.5.3
When using a 360-view of members in a portal implemented with an Ajax container that showed information in multiple tabs, tab switching was taking a lot of time even though the data was already in the memory. Updates have been made to improve performance.
INC-144924 · Issue 618733
Security alerts resolved for ActiveDocumentType
Resolved in Pega Version 8.5.3
SECU0001alerts indicating "HTTP Request Corrupted" were seen in the log files. These were related to the pyActiveDocumentType properties which are included in an Ajax request, and were caused by a condition where a new thread request results in an unexpected property check that encounters a clipboard which doesn't have any pages created for that thread. To resolve this, the pyActiveDocumentType properties have been added to an allow list to handle the unexpected properties check.
INC-144951 · Issue 601975
Updated specificity for custom-format inputs
Resolved in Pega Version 8.5.3
After upgrade, custom formatting for a link control was not working in the skin or during runtime. This was an issue where identical format names used for links and text components caused selectors from the text area to take precedence over link styles, and has been resolved by updating styles to increase specificity for inputs instead of links.
INC-145467 · Issue 617215
isDCSPA flag added to ensure correct harness after reload
Resolved in Pega Version 8.5.3
When moving from a Process Flow to a Screenflow configured with tabbedscreenflow7, the first reload caused a switch to a Perform Harness that resulted in the error "Unable to open an instance using the given inputs", and footer buttons disappeared until multiple refreshes were done. This was an issue specific to the environment configuration at the site, but to avoid future issues a code update has been made that will add the isDCSPA flag if the value is not present in the parameter page.