INC-232079 · Issue 741121
Clipboard page instance resolution simplified
Resolved in Pega Version 8.8
Previous work related to removing duplicate clipboard page creation from the pyInstanceInfoForUpdate list in order to resolve out of memory issues has been further updated to address a missed use case. While finding a matching instance with same className during instance list resolution, fault logic was leading to the same java object instance being updated N times and added N times to a linked list. This caused unnecessary complexity and has been resolved by removing the matching instance logic and instead creating items for each entry individually.
INC-232137 · Issue 734414
Improved handling for thread resolution issues
Resolved in Pega Version 8.8
Queue Processor/Dataflow was moving to STOPPED state due to failed records in its execution. Investigation showed there was a minor logic issue in the queue processor activity which allowed the Page-Remove step to be called even before the pages were actually created, and this has been resolved by improving the recovery from a cleared ThreadContainer which might cause thread resolution issues.
INC-234016 · Issue 738327
Improved handling for thread resolution issues
Resolved in Pega Version 8.8
Queue Processor/Dataflow was moving to STOPPED state due to failed records in its execution. Investigation showed there was a minor logic issue in the queue processor activity which allowed the Page-Remove step to be called even before the pages were actually created, and this has been resolved by improving the recovery from a cleared ThreadContainer which might cause thread resolution issues.
INC-234134 · Issue 742477
Connection list API call will be skipped when not configured
Resolved in Pega Version 8.8
An exception was appearing as part of Robotic Desktop Automation (RDA) flow whenever message service host was not configured. This has been resolved by skipping the connection list API call when the message service host is not configured. A specific Pega log and console log messages have also been added.
INC-178831 · Issue 680984
Ensured correct context for multi-select
Resolved in Pega Version 8.8
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-180100 · Issue 699838
Scrollbar persists for multiselect
Resolved in Pega Version 8.8
Selecting more than 20 values in the multiselect control caused the scrollbar to disappear. This has been resolved by removing a custom popover height calculation.
INC-183966 · Issue 676560
Corrected duplicated select file label reading
Resolved in Pega Version 8.8
When using a screen reader, the select file button label was announced twice on focus. Investigation showed this was caused by the helper text and tooltip having the same content which sounded like a duplicate reading. To resolve this, the text is now differentiated.
INC-183996 · Issue 669645
Step name given heading level for better accessibility
Resolved in Pega Version 8.8
When using the JAWS shortcut for navigating through headings, the Step name was not announced as expected. This was due to the Step name not containing the necessary code for a heading, and has been resolved.
INC-184307 · Issue 673228
Improved accessibility for overflow menu tab
Resolved in Pega Version 8.8
When a tabbled layout group has more tabs than will fit horizontally on the screen, icons appear to the left and right of the visible tabs to scroll through the available tabs along with a drop down list to select from all available tabs. Running the accessibility tool generated an error message for the down arrow button on the right. This was traced to a set tabindex 0 for unfocusable items, and has been resolved by adding tabindex="-1" for the overflow menu.
INC-186072 · Issue 677409
Updated ClientDynamicData HTML Rule
Resolved in Pega Version 8.8
After upgrading from Pega 7 to Pega 8, attempting to open an assignment on the staging environment showed a blank page. This was traced to the system trying to open a declare expression of "PegaComm-" class, and has been resolved by updating the pzClientDynamicData HTML Rule handling for the top level page and enabling the expression calculation checkbox in the Advanced tab of the pyCaseManger7 harness.