INC-205075 · Issue 698740
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.8
When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in the filter due to RRFilters_Logic reusing the strFieldName variable, and has been resolved by updating the variable handling to use a unique name, strPropName.
INC-205464 · Issue 721605
Performance improvements for KYC query
Resolved in Pega Version 8.8
The GetApplicationKYCTypes report definition was exceeding the default maximum elapsed time of 30 seconds, causing all cases which were part of the due diligence milestone in Client Lifecycle Management framework to be auto-completed. This has been resolved by improving the KYC Items query logic by removing mergeJoin and adding HashJoin Hints.
INC-209399 · Issue 708572
Handling added for indexing items exceeding Kibana max size
Resolved in Pega Version 8.8
Indexing cases was generating errors from Kibana indicating "Failed to index document: java.lang.IllegalArgumentException: Document contains at least one immense term in field="_m_MailBody" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped." To resolve this, if an embedded property exceeds the max length defined by Kibana, it will be truncated at 32k bytes in order to allow indexing to proceed.
INC-210837 · Issue 707178
DateTime property correctly formatted in Report Editor
Resolved in Pega Version 8.8
When a list report was created via the Report Editor, dragging and dropping a date time property which was embedded inside another page and choosing the format as Date and Time resulted in the property taking pxTextInput instead of pxDateTime. This has been resolved by updating the pzMergeAutoGenForProp activity to get the correct class name for embedded page properties.
INC-210989 · Issue 713050
Extremely long properties will be trimmed for export to Excel
Resolved in Pega Version 8.8
After creating a report definition that contained a column of more than 33,000 characters, exporting the report to Excel resulted in an exception. This was due to an Apache limit on xlsx files, and has been resolved by updating the ExcelDataGridGenerator.java file to trim more than 32767 characters of a property when exporting to Excel. This recreates the previous behavior of the export seen in Pega 7.
INC-212157 · Issue 721530
Report filter values correctly displayed
Resolved in Pega Version 8.8
The data page name was being displayed in report filters instead of actual values. This was traced to a missing step in the activity pzResolveCopyFilters which was needed to get the data page values in the report filter prompt, and has been resolved.
INC-215062 · Issue 722018
Removed ORDER BY clause duplication when using MSSQL
Resolved in Pega Version 8.8
After updating from Pega 8.4 to Pega 8.7, executing the query for the report definition generated the error "SQLServerException: Incorrect syntax near the keyword 'ORDER'." Investigation showed the ORDER BY clause was added to the Native SQL query from the standard dataflow background task and from the native SQL API as well when using an MSSQL database. This has been resolved by adding changes to restrict the order by clause if the SQL query has order by clause already for MSSQL.
INC-215209 · Issue 714621
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.8
When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in the filter due to RRFilters_Logic reusing the strFieldName variable, and has been resolved by updating the variable handling to use a unique name, strPropName.
INC-216416 · Issue 713848
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.
INC-217475 · Issue 719041
Corrected duplication of records in Elasticsearch
Resolved in Pega Version 8.8
After creating a dedicated index for a data class, modifying any data record for external Data/Work classes caused duplicate documents to be created in Elasticsearch. This has been resolved by updating the Reindex _id field to use the pzInsKey value instead of an auto-generated string. Once this update is in place, re-index is required to remove already created duplicates from the index directory.