SR-D61122 · Issue 522497
Multi-select in drop down displays subset of a value
Resolved in Pega Version 8.2.6
In a multi-select drop down, choosing a value (say EMEA-Interior) and then choosing a subset of that value as the second choice (ex, Interior), the second value was not getting selected. If the selection was performed the other way around (Interior first and then EMEA-Interior), it worked as expected. Analysis showed that patterns with similar names did not have the necessary differentiation in the system, and a comma has been added to the generated ID to identify similar values in multiselect capsules.
SR-D62361 · Issue 534809
Read-Only harness takes precedence over editable section with when condition
Resolved in Pega Version 8.2.6
Given a harness which was marked as Read Only and contained sections which were configured as editable based on some conditions, when the condition became true, the section became editable and ignored the read only conditions applied on the harness. Investigation showed that when a read-only 'when' rule evaluated to false, it rendered the layout in Edit mode instead of falling back to the read-only status of parent. This has been corrected by ensuring that when read-only evaluates to false, the system will fall back to the parent read-only status.
SR-D62436 · Issue 527201
Datetime control with Display details readonly works with Edit input
Resolved in Pega Version 8.2.6
After upgrade, a date time control was being reformatted incorrectly when it was set with Display details as read-only with an Edit input rule configured on the property to convert the date entered (ex, 112019 to 01/01/2019). To resolve this, a data-editinput attribute has been added in the control markup to support this configuration.
SR-D63416 · Issue 526522
Multi-select list control properly sets error message for server-side validation
Resolved in Pega Version 8.2.6
When using the Multi-select list control, client-side validation was working as expected but server-side validation was creating the Property-Set-Message error at Form level rather than Field level. This has been corrected.
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.