SR-D9242 · Issue 483172
Security improved for DownloadFromServiceExport
Resolved in Pega Version 8.1.6
In order to improve security, the activity “DownloadFromServiceExport” now requires authentication and explicitly blocks attempts to traverse up directories.
SR-D17306 · Issue 490919
RD pagination expanded to 1500 rows
Resolved in Pega Version 8.1.6
The default pagination enabled on the Report Definition was limiting the results to 50. This has been enhanced to a row limit of 1500 in report definitions pzGetAllPropertiesOfGivenClass.
SR-D17568 · Issue 498411
Handling added for interaction portal refresh containing many data parameters
Resolved in Pega Version 8.1.6
Attempting to refresh the browser when there were interactions opened in the Interaction portal and a huge amount of data on the parameter page caused the screen to blank and the interaction content was not displayed. Investigation showed that as part of the refresh, the displayOnPage GET request was sent with all of the parameters in the parameter page (data-model), resulting in a 400 Bad Request due to the browser URL length limitations. This has been resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case.
SR-D19602 · Issue 489990
GetDirections API enhanced to send exact current location to Google Maps
Resolved in Pega Version 8.1.6
The GetDirections API was not fetching the exact current location for Google Maps. In order to enhance precision, selecting the current location will use the navigation.geolocation.getCurrentPosition API to get the latitude and longitude position and send it as a saddr parameter to Google Maps.
SR-D13450 · Issue 488139
Corrected Query logging level for Populate_UsepxRequiredSkillsCount
Resolved in Pega Version 8.1.6
A Query was being logged with Logging level of Error in pzPopulate_UsepxRequiredSkillsCount. This has been corrected.
SR-D6769 · Issue 469285
Corrected tab closing issue for multiple clicks of Get Next Work
Resolved in Pega Version 8.1.6
While clicking multiple times very fast on a link configured with Get Next Work action, multiple tabs were getting opened with the same work object details and were not auto closing. This was traced to Issue with a stale conflictingHost in the handleGadgetLoad function, and updates have been made to the handleGadgetLoad function so it will get a new conflictingHost if the action is getNextWorkItem.
SR-D15391 · Issue 484921
Add row works as expected when using Embedded Elsewhere with a modal grid
Resolved in Pega Version 8.1.6
When using Embedded Elsewhere, add row was not working on the first attempt for a grid launched inside a modal dialog. Changing the focus then resulted in the added row appearing. This has been resolved by updating the timing for the performInsertAction in the ui_grid JS.
SR-D21332 · Issue 494518
Handling added for exceptions related to Microsoft Internet Explorer 11 grid cleanup
Resolved in Pega Version 8.1.6
Numerous exceptions generated from Microsoft Internet Explorer 11 related to pzPega_ui_grid were traced to a browser difference in timing logic related to grid cleanup. This has been resolved by adding a check to determine whether the grid is inside a defer-loaded section.
SR-D24083 · Issue 498488
Guardrail warning removed for setting filter by format on RD sourced grid
Resolved in Pega Version 8.1.6
After upgrade, use of the 'filter by format' (Configuration on table layout column) for grids sourced with report definition caused confusion in that the option now exists to either to see the value or the formatted value in the filter panel. Previously, a grid layout would show a date format in both the column of a grid and the filter of that column, but the filter changes produced a date format on the column within the grid but the date time format applied on filter of the column. This behavior change will be reflected in updated documentation. In addition, there is a workaround to recreate the old behavior by changing the column 'Date assigned' from a filter by value to format, but a moderate guardrail warning was created when filter by format was set on any column of a grid sourced to a report definition. This has been removed: when filter by format is selected, no guardrail warning will be displayed in design time.
SR-D25012 · Issue 499853
Column filtering updated to better handle merged columns
Resolved in Pega Version 8.1.6
When filters were applied to a grid containing merged columns, the columns next to the merged columns did not have the filter class applied. This was traced to a calculation of the index in getFilteredColumnIndex function which did not consider the merge columns use case, and the uigrid js file has been updated to correct this issue.