INC-169055 · Issue 646673
Performance improvements for database queries and archiving
Resolved in Pega Version 8.4.5
In order to improve the performance of database queries, repetitive unnecessary database calls have been removed, archival queries have been simplified, and diagnostic metrics were added. Optional batch requestors have been added to all archival services with their own DSS settings to allow processing more cases in parallel. It is recommended to create 2 additional indexes to help with the archival process. The indexes will be on:pegadata.pr_metadata (pyisparent, pyobjclass, pyarchivestatus) INCLUDE (pyinskey); pegadata.pr_metadata (pyisparent, pyarchivestatus) INCLUDE (pyinskey);
INC-169856 · Issue 649458
Personalized table sort order limited
Resolved in Pega Version 8.4.5
After implementing a personalized table, the query started adding more 'order by' sorts, causing system impact. This was traced to the pzPopulateSortOrder activity Implementation having different constants assumed for the same purpose (999 in one place and 99999 in another), and has been resolved by updating the logic in step 1 and step 2 to disregard sort orders higher than 999.
INC-174756 · Issue 650672
Queue processor correctly moves items to Broken Items
Resolved in Pega Version 8.4.5
When an exception occurred while Queue Processor processed an item, he queue item was not moved to Broken Items. The error " inconsistent datatypes: expected - got CLOB DatabaseException caused by prior exception" was generated. This has been resolved by modifying the NativeSQL builder and NativeSQLBatchExecutor to allow the batch of queries to be retried. Additional changes were also added for Oracle databases to identify the correct column types.
INC-175622 · Issue 652278
Screen reader announces report names
Resolved in Pega Version 8.4.5
An update has been made to pyReportBrowserItem to ensure names of the reports on the report browser are read correctly.
INC-183960 · Issue 675870
Condition check added to trigger search update
Resolved in Pega Version 8.6.4
Following work done to update deleting attachments for cases created through an email bot, search indexing was not updating automatically and a manual re-index was needed to allow the global search to work. This has been resolved with the addition of a condition check which will update the case when there is a delete operation done on the link page.
INC-198725 · Issue 707482
Elasticsearch will split queries to avoid URL length limits
Resolved in Pega Version 8.6.4
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-200973 · Issue 699266
Added handling for client-side validation errors in sub-reports
Resolved in Pega Version 8.6.4
When a sub-report was trying to access externally mapped fields or an optimized page property by JOIN of another class, the main report was unable to validate the Page property. This has been resolved by updating the activity code to handle client-side validation errors on main reports attempting to access the externally-mapped Page properties of another class in the sub-report.
INC-201625 · Issue 698655
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.6.4
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-202447 · Issue 698659
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.6.4
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
INC-202480 · Issue 699082
Resolved report filter section freeze
Resolved in Pega Version 8.6.4
When opening a report with a count column, changing the order of one of the report columns resulted in the report freezing and requiring the report to be closed and re-run. This was traced to a double filter popup appearing that did not close after the column sorting, which happened if the report definition was configured as a summary with an aggregated column such as "Count” combined with a "Do not display group headings" setting on the Report Viewer tab. To resolve this, a new step has been added in the Activity pzPopulateSortOrder to call the pzCancelFilterLogicChanges activity.