SR-D4829 · Issue 439802
Focus issue corrected for multiselect lists navigation
Resolved in Pega Version 8.1.5
Keyboard navigation (arrow keys UP and DOWN) were not working in Microsoft Internet Explorer and Google Chrome after selecting the value by using a mouse click in a multiselect control. After selecting the value using ENTER, keyboard navigation began working again. This was an issue where clicking an element from multiselect list caused the focus to shift to the body, and has been resolved by shifting the focus to the input element when the multiselect lists are clicked.
SR-C97772 · Issue 435631
Fixed Export to PDF page formatting
Resolved in Pega Version 8.1.5
A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected.
SR-D5079 · Issue 438383
Handling added for empty UILabel in grid fields
Resolved in Pega Version 8.1.5
When using a Datetime property with a default format, opening the filter popup and clicking on the 'select all' check box caused the format of the values to break. This was traced to ".pyUILabel" being passed as empty, and handling has been added for that in "pzUniqueValuesGridFields".
SR-C89628 · Issue 430886
Correct values are selected in auto-complete in list configuration after scrolling
Resolved in Pega Version 8.1.5
When a value from the second page of the source list in the auto-complete was selected, the prior value was getting selected and posted. As an example, if the (n)th value was selected by scrolling down the results in the list, the (n-1) value was getting selected and posted to clipboard. Investigation showed this occurred if autocomplete was configured with allow free form input ' no', and that results were not getting selected properly after first scroll when using list configuration. This has been corrected.
SR-C96703 · Issue 435743
CMIS Timestamp function updated to support more timezones
Resolved in Pega Version 8.1.5
When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.
SR-D1441 · Issue 438907
CMIS Timestamp function updated to support more timezones
Resolved in Pega Version 8.1.5
When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.
SR-D2796 · Issue 438394
Corrected Recents list resize issue in IE
Resolved in Pega Version 8.1.5
When using IE, opening the Pega Developer Studio to the landing page correctly resized the Recents list unless another tab was open. If there is another tab, the the resizing did not work and the scroll bar only allowed movement to the left. This has been corrected by setting the position to absolute for iframe(designer studio tabs) for IE.
SR-D1386 · Issue 444281
Warning message visibility conditions updated for Records Editor
Resolved in Pega Version 8.1.5
The Report Definition Result screen was showing the message "Warning : We were unable to create columns to match the new properties added. This will cause performance problems when using this data type. Please click here to fix this." Along with the RD results screen, this particular warning message was also shown in the Records tab of the respective Datatype. Initially, the Records Editor was developed for Designer Studio and Express usage. When the delegation functionality was later given to portals, the 'when' condition for the warning message was not updated to restrict displaying it to portal users. This has been fixed by updating the pzManageRecords section to properly manage the visibility condition of the warning message.
SR-C81185 · Issue 427995
Accessibility enabled Layout group tabs browsing corrected
Resolved in Pega Version 8.1.5
When using Layout group (Tab) or a Tabbed Layout for viewing client information in Tabs with Accessibility enabled, the system was reading each tab and its content but then focus was returning to the browser and tracing through all elements before moving on to the next tab. This was traced to an incorrect tabindex setting in the pzpega_ui_template_layout_header file, and has been fixed.
SR-C98177 · Issue 437225
Explicit modal close added to MSOFileTransferButtons control
Resolved in Pega Version 8.1.5
When using a MSOFileTransferButtons control that included buttons for Download Template and Import, clicking Import caused a popup for File Upload to appear with two options - Upload and Cancel. On clicking 'cancel', an Invalid Static Content error was thrown. This was traced to legacy code interaction issues with newer features, and has been resolved with the addition of a custom script to close the modal on click of the cancel button.