SR-131985 · Issue 195991
Sorting now working with filtering and pagination for RD
Resolved in Pega Version 7.1.8
Using filtering and pagination on Report Definition and then sorting on one of the subpages caused the error "no results found". This was an issue with the page index not being reset to 1 on apply of modal dialogue, and has been corrected.
SR-126901 · Issue 190595
Handling added for temp install directory names with spaces
Resolved in Pega Version 7.1.8
If the install directory name contained spaces, the install failed at the point where the directory was used as a script parameter due to the parsing handling the name up to the space as one parameter and after the space as another parameter. In order to resolve this, handling has been added to allow temp directory names with spaces.
SR-126901 · Issue 190603
Handling added for temp install directory names with spaces
Resolved in Pega Version 7.1.8
If the install directory name contained spaces, the install failed at the point where the directory was used as a script parameter due to the parsing handling the name up to the space as one parameter and after the space as another parameter. In order to resolve this, handling has been added to allow temp directory names with spaces.
SR-126980 · Issue 192477
Chart control validation updated to handle aggregate functions
Resolved in Pega Version 7.1.8
When a chart control contained a Report definition with COUNTDISTINCT in the summarize field, the chart was not displayed at runtime. Manually executing the Report Definition displayed the data and the pie chart as expected. This was found to be an issue with chart control not rendering the chart at run time if the underlying RD source contained an aggregate function. To correct this, the pzIsChartReportColumnValid validate rule has been updated.
SR-126980 · Issue 190876
Chart control validation updated to handle aggregate functions
Resolved in Pega Version 7.1.8
When a chart control contained a Report definition with COUNTDISTINCT in the summarize field, the chart was not displayed at runtime. Manually executing the Report Definition displayed the data and the pie chart as expected. This was found to be an issue with chart control not rendering the chart at run time if the underlying RD source contained an aggregate function. To correct this, the pzIsChartReportColumnValid validate rule has been updated.
SR-127180 · Issue 192478
Modified display of Listview filters to show action buttons
Resolved in Pega Version 7.1.8
After upgrading, Listviews used to generate reports that included filtering were not displaying the "Apply" and "Cancel" buttons in the drill-down pop up. To resolve this, the setscrollingDIVHeight API has been modified to properly display the content.
SR-127202 · Issue 192389
Join and Like filters tuned for Listview
Resolved in Pega Version 7.1.8
Listview join filters with LIKE operations were not performing optimal SQL queries, impacting system performance. This has been tuned to improve the system response.
SR-127210 · Issue 190272
Added table-based cataloging
Resolved in Pega Version 7.1.8
The Update Manager catalog has been updated to reside in the Pega database instead of in the file system. This will facilitate cataloging in a multi-node environment, allow for reporting and other visibility into the catalog itself, and improve performance of dependency checking.
SR-127237 · Issue 190840
Time-related RUFs now use operator's time zone
Resolved in Pega Version 7.1.8
Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone
SR-127319 · Issue 197788
Updated cache searching for Obj-Browse on a class mapped to external table
Resolved in Pega Version 7.1.8
Unnecessary queries were being fired while using Obj-Browse on a class mapped to external table. This was caused by a class mapped to an external table and using Obj-Browse on that class fired queries to the metadata to get the columns instead of searching in the caches. The system has been updated so that the caches are read instead of firing querying the metadata every time to get the list of columns.