SR-D22225 · Issue 504357
Added handling for iPad special characters in any key event
Resolved in Pega Version 8.4
When using an iPAD, there were 5 characters that were not caught when typed by the anykey event on a text control that was supposed to take only numeric data. The control worked as expected on iPhone. Investigation showed that the Keycode is 0 in the event object for some special characters with the iPad, and this has been resolved by using key instead of depending on keycode for those special characters.
SR-D43551 · Issue 511241
Added handling for iPad special characters in any key event
Resolved in Pega Version 8.4
When using an iPAD, there were 5 characters that were not caught when typed by the anykey event on a text control that was supposed to take only numeric data. The control worked as expected on iPhone. Investigation showed that the Keycode is 0 in the event object for some special characters with the iPad, and this has been resolved by using key instead of depending on keycode for those special characters.
INC-215582 · Issue 712287
Cosmos calendar icon handles allow entry set to no
Resolved in Pega Version 8.8
When using the Cosmos theme, the Calendar icon became disrupted when "allow text entry" option was set to "no". This has been resolved.
INC-179478 · Issue 662927
Handling updated for progressive load on scroll in repeating dynamic layers
Resolved in Pega Version 8.7
When using progressive load on scroll on a repeating dynamic layout with a bar graph control, the bar which was loaded earlier was being removed during scrolling and only the current page's bar graph was displayed. This was traced to the page load and refresh handling in repeating dynamic layers, and has been resolved by modifying the logic to use a partial-refresh when appropriate.
SR-D39601 · Issue 509519
RRDisplaySection made available to assist Edge compatibility
Resolved in Pega Version 8.4
When the Pega Platform was being used with Microsoft Internet Explorer Compatibility Mode ON, it was not possible to use the select filter gadget due to a browser compatibility issue: enabling the filter condition for the report definition caused the SelectValues button to stick in loading mode when clicked. Changing the Microsoft Internet Explorer Document Mode for Harness pzRRDisplaySection to IE=Edge corrected the issue, but the rule was final. To resolve this, the pzRRDisplaySection has been made available to allow override for customers still using IE.
SR-D39601 · Issue 509518
RRDisplaySection made available to assist Edge compatibility
Resolved in Pega Version 8.2.4
When the Pega Platform was being used with Microsoft Internet Explorer Compatibility Mode ON, it was not possible to use the select filter gadget due to a browser compatibility issue: enabling the filter condition for the report definition caused the SelectValues button to stick in loading mode when clicked. Changing the Microsoft Internet Explorer Document Mode for Harness pzRRDisplaySection to IE=Edge corrected the issue, but the rule was final. To resolve this, the pzRRDisplaySection has been made available to allow override for customers still using Microsoft Internet Explorer.
INC-182375 · Issue 664344
Report filter description correctly displayed
Resolved in Pega Version 8.7
When a function alias was used in the filter of a report definition without the caption and with some value assigned, the FilterName was not getting displayed when the report was run. This has been resolved by updating RRFilters_Logic.
SR-D45622 · Issue 521662
Sorting on Grid works with declare expression property
Resolved in Pega Version 8.4
If a property with a declare expression was used in a column, the sorting on that column was not working. This was traced to reference errors when Grid used the engine API pega.sortPageList to sort the page list / data page, and has been corrected.
SR-D28293 · Issue 498235
Pega Survey answer values support special characters
Resolved in Pega Version 8.4
When using a Complex radio control (RadioButtonComplexQuestionSurvey), a selected option that used answer values containing special characters was cleared on refresh. This was traced to a mismatch between strAnswer and strValue in the control logic, and has been corrected.
SR-D16624 · Issue 512128
Table layout filter popover position corrected for Pega mashup
Resolved in Pega Version 8.4
When using an exposed harness with table layout using Pega web mash up, the mash up worked but the apply and cancel buttons were not visible when any column was clicked to filter the result. This was traced to the filter popup having a hardcoded position offset set in its div element, and has been resolved by delegating the responsibility of the filter popover height calculation to the popover.