INC-180482 · Issue 677878
Browser compatibility update for setActivityAction
Resolved in Pega Version 8.5.6
After update, the Parameter Configuration popup was blank when using Microsoft Internet Explorer. This was traced to security updates that utilized the SafeURL.prototype.setActivityAction containing the startsWith API which is not supported by Internet Explorer. To resolve this, startsWith has been replaced with indexOf for cross-browser compatibility.
INC-181389 · Issue 668676
Unused class reference removed from CaseActionArea
Resolved in Pega Version 8.5.6
The rule Work-.pyCaseActionArea in Theme-Cosmos was logging error messages related to "clipboard.InvalidParameterException: Class not defined in dictionary: PegaMKT-Work" when opened in Dev Studio. This was traced to a reference to the section "pyCaseActionArea" which was not present by default in PegaMKT-Work, and has been resolved by recreating the section "pyCaseActionArea" to remove the unused class reference.
INC-181453 · Issue 669283
Text errors corrected for Pega Knowledge portal editing tools
Resolved in Pega Version 8.5.6
The Pega Knowledge portal had two errors in the content creation menu: the word "Title" was not translated in the "add a link" pop-up, and there was a typo in the word "paragraph" in the text editor item format drop down menu. These have been corrected.
INC-181890 · Issue 678586
Corrected missing space in mobile tab header
Resolved in Pega Version 8.5.6
When layout group (tab) was used with "Icon or value type" set as property or constant, the tab was missing a space between the icon/value and tab name. This has been resolved.
INC-182726 · Issue 677529
CORS DSS settings corrected for Constellation
Resolved in Pega Version 8.5.6
After moving to the new HIPPA edition, the developer work area in Constellation appeared as blank under Channel-Portal-Landing Pages. This was traced to a DSS setting issue when using cross-origin resource sharing (CORS), and has been resolved.
INC-182803 · Issue 679723
SearchKeyword assed to HandleInput allow list
Resolved in Pega Version 8.5.6
After creating a section and placing a template grid with a button to refresh the section on click, clicking the button generated a SECU0001 alert. This was traced to gridMetadata_(uniqueID).pySearchKeyword not being registered when the property is part of a form data post request, and this has been resolved by adding pySearchKeyword to the allow list in HandleInput.java.
INC-183163 · Issue 676251
Optimized table search updated
Resolved in Pega Version 8.5.6
Search functionality that can be enabled from tables after selecting the "Optimize" checkbox was not working correctly. This was traced to a potential issue getting the search parameter passed into the activity the section uses, and has been resolved by updating the system to get the element from pega.ctx.dom when pyFlowActionHTML div does not exist.
INC-183672 · Issue 701867
Corrected vertical scroll bar for iPad Mashup page
Resolved in Pega Version 8.5.6
After update, the vertical scroll bar shown on the Web Mashup page in Apple Safari on iPad continued to increase and showed excessive blank space. This was caused by the iframes,section height being considered as the iframe height, and has been resolved by setting the section height as 'auto' in case of mashups.
INC-184104 · Issue 682355
Cosmos Report Browser list updates during current session
Resolved in Pega Version 8.5.6
The Cosmos Report Browser list section was using a cached list of reports that did not update to reflect created or deleted reports until after logout and new login. This has been resolved by adding the pzInvalidateRBDataPages activity for harness initialization to update the reports list during the current session.
INC-184109 · Issue 671192
Handling updated for customDateTime formatting
Resolved in Pega Version 8.5.6
When a feature date was entered, for example as 2021/07/29 12:00:00 AM, changing any other property caused the time to be off by 4 hours and display as 2021/07/28 08:00:00 PM. Investigation showed this was caused by the parameters being passed in an incorrect order while calling pega.ui.Formatter.formatDateTime() in combination with customTimeZone, and has been resolved.