SR-130224 · Issue 200002
Fixed class pickup when Ticket Urgency is used as reference
Resolved in Pega Version 7.1.8
It was not possible to convert a summary report to a list report if the report had Ticket.Urgency as a reference and Ticket was a single page pointing to data class type property in the work class. This was traced to the drill down picking up the Urgency property from the work class, and has been resolved.
SR-130401 · Issue 201418
Fixed listview filtering header shift
Resolved in Pega Version 7.1.8
When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.
SR-130401 · Issue 200029
Fixed listview filtering header shift
Resolved in Pega Version 7.1.8
When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.
SR-131323 · Issue 201113
RD operator filter max value increased
Resolved in Pega Version 7.1.8
The limit for items displayed by the RD filter pxCreateOperator has been increased to 1000.
SR-131522 · Issue 200840
Localization added for report name tooltips
Resolved in Pega Version 7.1.8
Tooltips in reports for report names are now available for localization.
SR-131538 · Issue 200108
Removed extra blank line from exported SV report
Resolved in Pega Version 7.1.8
An Excel spreadsheet exported from any Summary View (SV) report contained a blank row at the top. This has been corrected.
SR-132135 · Issue 202410
Smoothed 'save as' for private reports without checkout privs
Resolved in Pega Version 7.1.8
When a user did not have checkout option either at the operator level or at the design time rule-set level, trying to use 'Save As' on Report definition rules reports in Private category resulted in an error but actually saved the report at the back end. Opening the Case Manager portal and trying to do a 'save as' of an existing report led to the report category being populated as private but the standard categories got populated in the drop down. If OK was clicked, then the standard categories were replaced with private category. To improve this, a check has been added to detect a non-developer operator, who is then allowed to save in their personal category.
SR-132569 · Issue 201349
Corrected portal refresh after chart unload
Resolved in Pega Version 7.1.8
When a chart is unloaded, a separate request was sent to the server to remove all chart-bounded data pages, i.e. pzRuntimeChartCleanup. If nothing is returned, the ActivityStatusSuccess Message was seen instead of the Work Item when the portal was refreshed. The API has been updated to return the correct information.
INC-185824 · Issue 676628
Corrected filtered column list sorting in Report Browser
Resolved in Pega Version 8.8
Sorting was not working in Report Browser for a column list when a filter category was selected. This has been resolved by modifying the pzReportListSort activity to set the correct parameters in step-1 and setting pzSetCategoryParam to retain the sortTitle parameter in step 1 with an added step -2 to call the pzReportListSort activity.
INC-198725 · Issue 707483
Elasticsearch will split queries to avoid URL length limits
Resolved in Pega Version 8.8
Elastic Search Functionality was not working and showed the status as Offline. Investigation showed that when an external Elasticsearch setup had an index prefix length = 200 and a large number of dedicated indexes, the error "too_long_frame_exception, reason: An HTTP line is larger than 4096 bytes" was generated. In this case, the system was working with approximately 87 dedicated indexes and the name for each of them was sent over the URL, resulting in this error message. This has been resolved by updating the system to split queries so as to not exceed the HTTP line limit in Elasticsearch.