INC-159008 · Issue 634767
Resolved unregistered request for Dev Studio clipboard viewer
Resolved in Pega Version 8.3.6
After upgrade, running a report in Dev Studio and then clicking to start the tracer or clipboard did not open, but instead generated the error "Unregistered request encountered." This has been resolved by adding a pySecureFeatures check in step1.
INC-164924 · Issue 638913
Serbia added to country codes list
Resolved in Pega Version 8.3.6
The CountryCode for Serbia (SRB) has been added to the existing country codes.
INC-165468 · Issue 642241
Live UI option works with embedded iframe objects
Resolved in Pega Version 8.3.6
When the LinkedIn gadget was enabled in utility or a YouTube video was embedded in an iframe, the live UI button was not working. This has been resolved by updating the implementation to use getFrameList to loop through frames and check the frameElement.
INC-167471 · Issue 638870
Resolved focus for new s-case
Resolved in Pega Version 8.3.6
After creating an s-case by using the keyboard, the focus jumped to add task instead of newly added s-case page. This was traced to the 'if' condition in focusFirstElement method becoming true for all touchable devices including desktop with touch enabled, causing the focus method on the first element to not be executed. This has been resolved by adding an additional conditional to check whether the device has touch enabled and is a mobile device.
INC-167471 · Issue 639257
Touch Modal gets focus to be read by JAWS
Resolved in Pega Version 8.3.6
A Modal on a touchscreen device was not being read by JAWS. This was an issue with the accessibility focus combined with the touch elements, and has been resolved by fixed by adding a check for touchable devices.
SR-69015 · Issue 619995
Unescaping characters implemented for expressions
Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6
An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.
SR-D53176 · Issue 541796
Error when adding function filter will persist
Resolved in Pega Version 8.4.1
When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.
SR-D64231 · Issue 539235
Export to Excel cell style control added
Resolved in Pega Version 8.4.1
If a column was formatted with an auto generated numeric control, a new cell style was generated for every row during the export to Excel process. Since there is a limit on the amount of cell styles, once the number of rows in the file was greater than 64000 an error was generated. To resolve this, the system will disable the creation of a new cell style for every instance when an auto-generated numeric control is used.
SR-D65327 · Issue 534572
Backspace keydown handler updated for all textinput modes
Resolved in Pega Version 8.4.1
Attempting to use the Backspace key to remove input from a number cell (either Integer or Decimal) did not work. When the action was performed by a Manager, the Backspace key works as expected. Investigation showed the logic in the keydown handler for the backspace key in pega_report_events.js was only ignoring the e.preventDefault() call when the textinput node type was text, not number or other input types. To correct this, the keydown handler has been updated so the backspace key in pega_report_events.js maintains the default backspace functionality for all textinput modes, not just those of type 'text'.
SR-D69098 · Issue 534043
Export to Excel works for for report definition with duplicate columns
Resolved in Pega Version 8.4.1
After adding a date column to a report definition (2nd column in the report), the data displayed correctly in the UI but Export to Excel failed with the error "Section 'pzRDExportWrapper' execution error on page '' of class 'Rule-Obj-Report-Definition'. : The Reference .pyDateValue(2) is not valid." This was traced to an out of bounds exception thrown if there were two or more columns with the same calculation. When preparing for export, the column with the duplicate calculation would not get added to the map of report UI fields. To resolve this, the system has been updated to allow report definition columns with the same calculation to be properly mapped to a UI field.