SR-D64244 · Issue 532982
Support added for recording with sIngle-option radio button inside a repeating grid
Resolved in Pega Version 8.2.6
Recording a test case was not working when a single option radio button (i.e., radio button control with property of type boolean) was configured inside a repeating grid. In this case, it was found that the Radio button markup did not have a data-test-id attribute for non-template single option; this has been added.
SR-D64667 · Issue 531806
Cursor issue resolved for tab within expandable row
Resolved in Pega Version 8.2.6
When pressing the “Tab” key on an expanded row, the cursor was not moving inside the expanded part. This has been fixed by adding a check to get the correct first focusable element.
SR-D64694 · Issue 533961
Check added for Turkish locale in Firefox
Resolved in Pega Version 8.2.6
When using Firefox in the Turkish locale, attempting to open worklist subsets or edit tables in a modal dialogue caused the browser to hang. This was traced to the character conversion process in the browser and has been resolved with the addition of a check.
SR-D64945 · Issue 534323
Accessibility enhanced for multiselect
Resolved in Pega Version 8.2.6
Aria attributes for multiselect items and container have been added to enhance accessibility.
SR-D65034 · Issue 529565
Check added for malformed query on F5 refresh
Resolved in Pega Version 8.2.6
A 500 Internal Server Error occurred when F5 was clicked to refresh the screen. This was traced to a malformed URL that was missing the '?' before the query parameters, and has been resolved by adding a check in the pzpega_ui_dynamicContainer_lite js file replaceHistory method that will insert the question mark if it is not present.
SR-D65086 · Issue 526596
Harness context will be stored to handle on click executed outside of the Ajax Container
Resolved in Pega Version 8.2.6
An exception was generated in the interaction portal on execution of a post-value action for the on-change event on a text-box in the service case: "Failed to find instance Work-Interaction-Research.EmailBodyRTE of type Rule-HTML-Section". This was traced to a condition where clicking outside of the Ajax Container context to trigger the change caused the Events code to execute the event in the active context when the active context had already been changed by clicking outside of the AC. To avoid this, the system will store the harness context in the event object using pega.ctxmgr.getContextByTarget(target) API. Additional changes were also made to handle the context switching in case of post value when the blur triggers a change in context.
SR-D65917 · Issue 529627
Cross-site scripting protection added to ClientDynamicData
Resolved in Pega Version 8.2.6
Cross-site scripting protection has been added to various parameters in the pzClientDynamicData HTML rule.
SR-D66095 · Issue 529706
Cross-site scripting security added to Richtext Editor
Resolved in Pega Version 8.2.6
A scenario where HTML objects could be copied and pasted into CKEditor and the click action modified to perform different actions was traced to Pega event attributes present in the rich-text editor content. This has been corrected by blacklisting Pega event attributes like data-click, etc. In
SR-D66436 · Issue 529671
Correct Value shown for Helper Text controls with labels
Resolved in Pega Version 8.2.6
Helper Text sourced from a field value was displaying the field value's 'Translate From' value rather than the 'Translate to' value. Analysis showed that the 'title' attribute of the corresponding icon on the DOM was being populated differently depending on whether it was a control with labels (not working) or a caption on a checkbox control (worked as expected). To address this, a check has been added for datetime and checkbox controls to send fieldname as pyCaption and pyActionPrompt respectively instead of pyTooltip to resolve the value.
SR-D68277 · Issue 541815
Added logoff check for requestors
Resolved in Pega Version 8.2.6
After upgrade, the error "java.lang.InterruptedException. Requester has been destroyed" was appearing in the logs. Investigation showed this was related to unregister requests being submitted after logoff, and has been resolved by updating the system to check for logout before sending unregister requests.