INC-234874 · Issue 739874
Cursor moves via arrow buttons
Resolved in Pega Version 8.8
Using the keyboard arrow buttons to navigate between numbers was not working. Nothing happened when clicking on the left arrow, and clicking on the right arrow moved the cursor to two digits. This has been resolved by updating pzpega_control_textinput.
INC-234958 · Issue 742548
Corrected menu item name display and styling for expand icon
Resolved in Pega Version 8.8
After update, a Menu Item with Sub Menu items present did not display the arrow icon to indicate the presence of Sub Menu Items. In addition, the Menu Label was shown twice on click of the parent Menu Link. These have been corrected.
INC-235161 · Issue 743708
Resolved validation check freeze for Dynamic Layout Group
Resolved in Pega Version 8.8
After creating a multi-step form where step 1 had a Dynamic Layout Group(tabbed) that used form fields configured with validations, clicking next with empty/invalid values in the form intermittently caused the screen to freeze and a javascript exception was logged. This was traced to a missed use case related to templates in the childNode, and has been resolved by adding the necessary safe checks in lgtemplate and lgcelltemplate.
INC-236451 · Issue 745819
Backbone.js updated
Resolved in Pega Version 8.8
The backbone.js package has been updated to the most recent version.
INC-237221 · Issue 743444
Security improvement for Currency control
Resolved in Pega Version 8.8
A potential cross-site scripting issue related to readonly formatting for the Currency control has been resolved.
SR-A8538 · Issue 222591
RepeatIndex generation improved
Resolved in Pega Version 8.1
Controls in a triple layout included in a row repeat did not have matching unique IDs and label for attributes. This was due to incomplete generation of the repeatindex for the ID, and has been fixed.
SR-C4920 · Issue 347563
Grid Header checkbox behavior modified for consistency
Resolved in Pega Version 8.1
Unexpected behavior was seen when clicking on the Checkbox present in Header: all other checkboxes changed their state (which was expected), but if the the Readonly checkbox was checked it was also changing the state the first time (which was not expected). After this first state change, the read-only checkboxes were not changing state (which is correct behavior). Previously, the behavior of Select All / CheckAll checkboxes was as follows: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked irrespective of their DISABLED state The behavior has now been changed as below: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked only when they are NOT disabled
SR-C7762 · Issue 350154
Commas removed from filter values to resolve validation errors
Resolved in Pega Version 8.1
When using a Grid layout configured in a section rule, clicking the Filter option and entering a comma separated value in the "To" field in a decimal-type column resulted in an "Invalid numeric range" option message. No error was seen if comma separated values were entered in both the "To" and "From" fields. Because the checkRangeFilter() function in ui_grid.js uses parseFloat() API to extract the decimal content entered in the search boxes, decimals after commas are ignored and validation failed due to the fields not matching. This issue has been fixed by implicitly removing any commas entered by the user.