SR-A95224 · Issue 262257
Fixed dropdown filtering logic
Resolved in Pega Version 7.2.2
When a grid was configured with source as pagelist and cells with dropdowns as controls in it, attempting to filter the dropdown list displayed the filter window instead of the options in dropdown. This was caused by the filter logic not considering the filter by value setting and using the pyUILabel property by default for showing the unique values in the filter pop-up. To correct this, the system will consider the value of pyShowFilterUIBy while also allowing certain controls to maintain their format.
SR-A87970 · Issue 255816
New window alert shows with accessibility mode
Resolved in Pega Version 7.2.2
When a new harness was opened in an "accessible" mode, the new window alert was not thrown when opening the new window in a pop-up or when opening in a new tab. This has been fixed.
SR-A89711 · Issue 257213
New window alert shows with accessibility mode
Resolved in Pega Version 7.2.2
When a new harness was opened in an "accessible" mode, the new window alert was not thrown when opening the new window in a pop-up or when opening in a new tab. This has been fixed.
SR-A85709 · Issue 255759
Cleared erroneous dirtycheck popup on DropDown using lazyload
Resolved in Pega Version 7.2.2
When a pxDropDown was configured with load mode "After screen renders", the "selected" attribute was not correctly set on the HTML and the dirtyCheck failed even when the values were saved. This was due to the "Selected" attribute on options tag not being set properly when the dropdown mode was set to lazyload (after screen render), and has been fixed.
SR-A92680 · Issue 263151
Removed duplicate repeat grid header
Resolved in Pega Version 7.3
An extra Grid Header Title was created when allow refresh on update was checked in a repeat grid configured for row editing via modal dialog. This was due to a place holder div error, and has been corrected.
SR-A77307 · Issue 260263
Null check added for selectNodes extraction
Resolved in Pega Version 7.2.2
When an assignment contained a field with custom control that included 'ClientValidation' with 'Activate input formatting' selected for this field, attempting to change the field or submit the assignment generated the JS error 'Unable to get property 'selectNodes' of undefined or null reference'. This has been resolved by adding a null check to the selectNodes extraction function to handle empty values for the returned object.
SR-A77307 · Issue 260728
Null check added for selectNodes extraction
Resolved in Pega Version 7.2.2
When an assignment contained a field with custom control that included 'ClientValidation' with 'Activate input formatting' selected for this field, attempting to change the field or submit the assignment generated the JS error 'Unable to get property 'selectNodes' of undefined or null reference'. This has been resolved by adding a null check to the selectNodes extraction function to handle empty values for the returned object.
SR-B339 · Issue 270442
Enhancement added to place icons on tabs with client-side errors
Resolved in Pega Version 7.2.2
When client-side errors occurred on inactive tabs in a tabbed screenflow, there was no indication (for example an alert icon) of which tab had an error, only the pop-up error message "Please correct flagged fields before submitting the form!". An enhancement has been added to place an error icon on the tabs where the client-side errors have occurred.
SR-B385 · Issue 270797
ASCII characters properly displayed in dynamic layout headers
Resolved in Pega Version 7.3
When using a field value that contains special characters like + and = to display the header value of a dynamic layout the characters were being converted to their encoded ASCII characters on screen (ex [&] instead of [&]). This was traced to the Field Value text being encoded twice, and the GridHeaderElements function has been updated to correct this.
SR-A88617 · Issue 259450
Scroll bars made consistent for RTE content
Resolved in Pega Version 7.2.2
When content is entered beyond the boundaries of the Rich Text Editor (RTE) control, scroll bars appear to view the content. When attempting to print the case while in the Review/ Confirm harness with the same field, the complete content of the case was not shown on the print screen (scroll bars were still present). When the item was printed, the RTE contents did not print at all. The scroll bars are added by the browser to handle word wrap, but they are not used for RTE elements which have 'contenteditable' set to false. To resolve this, word wrap has been added for RTE in review and print options so browsers will behave consistently for elements which have the 'contenteditable' attribute as false.