INC-160624 · Issue 633084
HTTP Strict Transport Security update
Resolved in Pega Version 8.5.4
An update has been made to increase the max age of the HTTP Strict Transport Security (HSTS) header parameter from 7 days to 1 year.
INC-160839 · Issue 643469
Session timer corrected
Resolved in Pega Version 8.5.4
Configuring pxsessiontimer in the Portal header to log users off after 30 minutes was not working as expected: users were still logged in the next day or after keeping the session idle for more than 30 minutes. After waking up the system, it was possible to search clicking on the search results resulted in being logged out. This was traced to the ShowLogoffTimer activity not being correctly registered, and has been resolved.
INC-160843 · Issue 631727
Performance improvements for multiple visibility expressions in repeating structures
Resolved in Pega Version 8.5.4
After upgrade, performance degradation was seen and PEGA0069 alerts appeared frequently. Investigation traced this to performance issues with the expression evaluation on the client when there were multiple visibility expressions in the repeating structures. To resolve this, updates have been made to the pzpega_ui_ExpressionEvaluator.js to reduce the number of calls to _getCtxElement( ) in side loops.
INC-161126 · Issue 631089
Edit validation message appears on Cosmos UI
Resolved in Pega Version 8.5.4
When using a flow action in Cosmos, validation messages did not appear on the UI as expected but an error would be thrown while clicking on the submit. This was traced to an unneeded visibility condition present on the section "pyCaseActionArea" when "pyCaseErrorSection" was included, and has been resolved.
INC-161409 · Issue 632725
Added handling for checkbox group to use form tag when field tag is not available
Resolved in Pega Version 8.5.4
After configuring the Checkbox group component from the UI gallery in one of the sections in an application built on Theme-Cosmos, the configuration worked as expected when creating a new case type, but opening this WorkObject from the Associated cases section on the child case caused behavior issues including being able to select select multiple options instead of a single radio button. Investigation showed this happened when navigating through the work flow under the Perform Harness, but worked as expected when navigating through the Review Harness. This has been resolved by modifying the selectors to target form tag if the fieldset tag is not available.
INC-161722 · Issue 632868
Resolved preview button issues with Microsoft Internet Explorer 11
Resolved in Pega Version 8.5.4
After opening the case from "My WorkList" when using Microsoft Internet Explorer 11, trying to go back to "My WorkList" /"Dashboard" to preview the case resulted in the preview button shrinking and the text not being completely visible. This was traced to the field -et being initially assigned to the text of the dom element in Internet Explorer, but then being removed while navigating within the pages. To resolve this, an update has been made so field-set is assigned to a variable and the same variable is assigned to the preview text.
INC-161757 · Issue 630690
CKEditor correctly formats copy and paste
Resolved in Pega Version 8.5.4
Formatted text from Micrtosoft Word was not retaining its format when pasted into the rich text editor. This was caused by the inch to px and pt to px conversions not happening properly for margins, and has been resolved by adding a margin fix for nested bullets and lists.
INC-161909 · Issue 635149
Upgraded pd4ml library to support Hindi text
Resolved in Pega Version 8.5.4
Some Hindi letters were not displayed properly in PDF . This was caused by Hindi text being only partially supported with earlier versions of the pd4ml library. It is now fully supported with the 4.0.9fx5 version, and the system has been upgraded to 4.0.9fx5 jar for better rendering of Hindi characters.
INC-161937 · Issue 640265
VMWare workspace One Mobile support added
Resolved in Pega Version 8.5.4
Support has been added for the VMWare workspace One Mobile app by updating the BrowserUtilsRuntime file to add the necessary user agent.
INC-161996 · Issue 636874
Mobile back button updated for case completed scenario
Resolved in Pega Version 8.5.4
Mobile back button updated for case completed scenarioIn a scenario when a case was resolved and assignments were removed from user pages, the hitting the back button presented the error: "unable to open an instance using the given inputs". This was a missed use case for using the back button on the mobile app after a case is completed, and has been resolved by modifying the back button action in this scenario from "window.history.back" to Cancel action.