INC-177104 · Issue 666332
Resolved-by field reflects queue processor close
Resolved in Pega Version 8.5.6
When a case was resolved by the queue processor, for example when the SLA ended and a case was automatically Resolved-Withdrawn by the system, the "Resolved by" field was blank. This was caused by the pyOperatorInfo control looking for the system account user data in the application users pool, and has been resolved by updating the control to display the localizable "System" name in this scenario.
INC-178417 · Issue 670111
Flag reset added for grid with 'Expand When'
Resolved in Pega Version 8.5.6
A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.
INC-178579 · Issue 657742
Corrected blue line showing on grid expansion
Resolved in Pega Version 8.5.6
When a grid configured on the portal had an overlapping case preview, a blue vertical line was displayed on the preview window when expanding a row. This has been resolved by increasing the z-index for the preview panel to cover the underlying grid resize indicator.
INC-178831 · Issue 680983
Ensured correct context for multi-select
Resolved in Pega Version 8.5.6
When using multi-select controls, there was an intermittent issue with selecting values using a mouse click. Using the tab key worked as expected. This was traced to the focus being event triggered multiple times so pega.ctx.dom returned undefined values in the second call.This has been resolved by focusing the target element before creation of capsule to ensure the context remains the same.
INC-179789 · Issue 659310
Tab focus sequence updated
Resolved in Pega Version 8.5.6
The keyboard tab sequence was not following a logical order when using the "Application" overlay accessed from the 9 dots in the top left. This has been resolved.
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.