INC-162649 · Issue 639397
DSS added for handling missing attachments
Resolved in Pega Version 8.3.6
When an S3 repository was configured as storage, some cases were not coming up in search and exception errors were seen in logs for a deleted attachment after every system restart/re-indexing of the search. Investigation showed these case objects were in the broken queue for pyFTSIncrementalIndexer due to a null pointer error encountered when indexing the attachment, and that the attachments were available in the repository but could not be read from the attachment repository during indexing. To resolve this, a new DSS setting has been added which allows selecting one of two behaviors:- Pega-SearchEngine indexing/distributed/fail_on_missing_attachment_file = true : broken item is generated, but with a meaningful error message. This is the default behavior - Pega-SearchEngine indexing/distributed/fail_on_missing_attachment_file = false: case is indexed, but without the problematic attachment. Error message is printed out to the logs.
INC-162968 · Issue 632476
Extra text seen in edit removed from Report Browser
Resolved in Pega Version 8.3.6
Extra Text reading 'BBBBBC' was appearing when editing Reports within Report Browser. This was due to extraneous test text input present within 'RRDataListHeader' HTML Rule, and this has now been removed.
INC-163160 · Issue 631476
Updated filter logic for filtering on a DateTime column
Resolved in Pega Version 8.3.6
When a class join was used in a report definition, the error "The Filter Logic used in the report is invalid" appeared while filtering rows of a report definition results on a DateTime column. This was a missed use case, and has been resolved by modifying pzGridSortPaginate to convert the data type value into the proper casing.
INC-169055 · Issue 646670
Performance improvements for database queries and archiving
Resolved in Pega Version 8.3.6
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);
SR-D91660 · Issue 555722
Updated document ID handling for deleting indexes
Resolved in Pega Version 8.3.6
When trying to delete a document for index name "work*", intermittent errors were seen indicating an invalid index name or index does not exist value. This has been resolved by updating the handling for delete by ID.
SR-132352 · Issue 202264
Corrected Filter criteria Pick Value button behavior
Resolved in Pega Version 7.1.9
The Pick Value filter criteria pop-up was only working if the property was a direct class property and did not work with an embedded property. This has been corrected.
SR-132827 · Issue 202511
Adding handling for 'today' date field in RD filtering
Resolved in Pega Version 7.1.9
The 'today' link in calendar popup selects the current date when clicked and automatically closes the popup, but attempting to use the 'today' link in a Report definition with a date field as a filter did not select the current date and did not autoclose. This has been corrected.
SR-132946 · Issue 202933
RD with multiple joins now displays all properties in Data Explorer to end user
Resolved in Pega Version 7.1.9
Given a Report Definition with two joins defined on it, the end user was not able to view or select from all of the properties from the joined classes due to the myStepPage adding entries outside of the WHILE loop. This has been corrected by updating the pzGetPropsForTreeGrid activity to handle this scenario by iterating through all of the join classes and showing them in Data Explorer.
SR-A1139 · Issue 204433
Ensured threshold checkbox honored in Report Wizard
Resolved in Pega Version 7.1.9
Validation errors were being generated in the custom report wizard when 'threshold' was not selected. This was an issue where the validations were being added without checking the value of the checkbox, and has been corrected.
SR-A1220 · Issue 204961
Corrected SQL exception on Monitor Processes reports
Resolved in Pega Version 7.1.9
Some Pega out-of-the-box summary reports under 'Monitor Processes' like "Created in last 30 days by Operator", "Created in last 90 days by operator, etc., were throwing SQL exceptions on drill down if they had data. This was caused by the DrillDown activity getContentWeekly that was being used for some of the SVs not having the flags pyCanUseVirtualList and pyUseVirtualList set to true, unlike the default DrillDown activity getContent. This was causing the query generated for DrillDown to have the prefix "PC0" only for the drilldown filter condition. This has been resolved by modifying getContentWeekly to set the flags properly.