SR-A17411 · Issue 234053
Alignment resolved for repeating grid headers
Resolved in Pega Version 7.2.1
Headers were mis-aligned in the UI Gallery for a repeating grid when the freeze header option was chosen along with pagination and width of the content. This was an issue with the initScrollbars function, and has been corrected.
SR-A17425 · Issue 233173
Memory leak fixed in Field Value Conclusion Cache
Resolved in Pega Version 7.2.1
A memory leak was found with Field Value Conclusion caching not being correctly cleared of the dummy conclusion values for null objects. This as been resolved.
SR-A17476 · Issue 234924
Autocomplete working on node level data pages
Resolved in Pega Version 7.2.1
The auto complete feature was not working if the Categorize search results option was checked on node level data pages. The SortClipboardData now has support for node level data pages categorization.
SR-A17488 · Issue 234010
Corrected truncation of localized text in Report Viewer filters
Resolved in Pega Version 7.2.1
The localized test "Select Values" text was being truncated in the Report Viewer filters were enabled. This setting has been updated to take the additional width without truncating.
SR-A17497 · Issue 234925
Enhanced column supports in 'Export to Excel'
Resolved in Pega Version 7.2.1
Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index, Associations, Sub Report, Functions and Embedded Properties.
SR-A17544 · Issue 236778
Removed pagination size restriction on listview if page size is set
Resolved in Pega Version 7.2.1
When an application had more that 50 data-types, not all data-types were shown in the application packaging wizard due to the page size being set to 50 while the list view function was set to return a maximum of 50 results if pagination was enabled. The pagination size limit on listview has been disabled in cases where page size is set in order to remove this conflict and display the results as expected.
SR-A17560 · Issue 234697
Added dynamic check to HarnessPurpose parameter
Resolved in Pega Version 7.2.1
If a main flow referenced a subflow with a parameter "HarnessPurpose" and value "Perform", accessing the subflow generated the error "Failed to find instance XXX-Work-Test.Param.HarnessPurpose of type Rule-HTML-Harness." This was an issue where the HarnessPurpose parameter caused a reset of the pxFormName property in the newassignPage, and this has been fixed by checking if the harnesspurpose is dynamic before setting the pxFormName.
SR-A17649 · Issue 233752
SQL generation modified for "Optimize for Reporting"
Resolved in Pega Version 7.2.1
After using the wizard to update Properties via "Optimize for Reporting", Report Definition will create SQL that is unique if the optimized property name is too long. This can result in the unique property name exceeding the 30 character field length, which then triggers the generation of a unique id with P +timestamp as the column alias name. Unfortunately, this means even if the same report is executed multiple times, the query would be different each time because of the column aliases and therefore the DB engine won't take the benefit of prepared statement caching and performance could be effected. To create the most effective performance, the column alias generation has been modified as below to make the column alias the same across multiple runs of RD: - using 25characters in propertyname and suffix it with index of the field location in RD select, L for list report - using 25characters in propertyname and suffix it with index of the field location in RD select, G for group fields in summary report
SR-A17654 · Issue 234844
Stack trace will not display in REST errors
Resolved in Pega Version 7.2.1
To improve security, the exception stacktrace generated by a REST Service response will not be displayed as part of the error. The message "An error occurred while processing the request. Please contact your Administrator." will be displayed instead, and the stack trace will be logged.
SR-A17654 · Issue 246367
Stack trace will not display in REST errors
Resolved in Pega Version 7.2.1
To improve security, the exception stacktrace generated by a REST Service response will not be displayed as part of the error. The message "An error occurred while processing the request. Please contact your Administrator." will be displayed instead, and the stack trace will be logged.