INC-217656 · Issue 722530
Elastic Search honors case sensitivity for custom data
Resolved in Pega Version 8.8
Case-insensitive search was not working for custom data dedicated indices which had the "Enable search results for all properties" option enabled in the Report Definition. Investigation showed that in the CustomSearchPropertyDefinitionFetcher class for all index properties, new SearchPropertyDefinition objects were created with caseInsensitive field set to false. This led in some cases to incorrect merge where it was expected the caseInsensitive field would be set to true. To prevent this, the CustomSearchPropertyDefinitionFetcher class has been updated so the caseInsensitive field for new SearchPropertyDefinition objects is set based on existing instances with the same pyPropertyName if such exists.
INC-217974 · Issue 715428
Handling added BIX extraction failure when called from custom activity
Resolved in Pega Version 8.8
After update, BIX extraction was failing but email from the schedulers indicated success. Investigation showed that when extract was called from a custom activity by calling pxExtractDataWithArgs, the stepStatusFail 'when' rule in the custom activity was not capturing all the exceptions specific to database extracts. This has been resolved by adding the necessary handling.
INC-218491 · Issue 717433
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-219697 · Issue 727794
Handling added for large BIX Postgres data sets
Resolved in Pega Version 8.8
BIX extracts were causing timeouts or JVM out of memory errors. This was traced to the Postgres JDBC driver ignoring fetch size in auto-commit transaction mode, which led to everything being loaded into memory at once. To resolve this, changes have been added to support fetch size for large results when using PostgreSQL database for BIX Extraction.
INC-220663 · Issue 724471
BIX -J usage for DST can be used in Pega 7 mode
Resolved in Pega Version 8.8
After upgrade, there was a difference in the handling for a time zone with DST when executing a BIX extraction rule through command line arguments like -J with short form. In Pega 8.5+, -J CST6CDT always displays Date time to CDT; In Pega 7, -J CST6CDT displays Data Time based on CST or CDT (i.e. before daylight savings or not). This was due to changes made to set the time zone to address a different issue. While there is a workaround of using -J America/Los_Angeles, modifications have been made to support DST in the PEGA 7 format while running the BIX extraction rule from command line or with a "pxExtractDataWithArgs" activity with "-J" option.
INC-222237 · Issue 727705
Handling updated for space in report filter value
Resolved in Pega Version 8.8
The Report filter was not working correctly if there was a space in the filter value. To correct this, an update has been added which will add parentheses so the filter value is treated as a single value if pyUseTokenizer is set to false, the filter is not a security filter, and the filter value contains whitespace.
INC-223448 · Issue 722481
Documentation updated to clarify a complete reindex is required for search landing page after cleanup
Resolved in Pega Version 8.8
The "Rebuilding search indexes from the user interface" article has been updated to indicate that after the index directory cleanup, the search landing page reindex will only be available once the complete reindex is completed. If individual classes are reindexed, the state will still be incomplete.
INC-230454 · Issue 732407
Corrected Custom Search Property handling with embedded properties
Resolved in Pega Version 8.8
While using full text search, Enter Action set was not passing data entered in the search property. Investigation traced this to an issue with the Custom Search Property (CSP) transformer combined with the enabled DSS indexer/srs/includeCSPEmbeddedPropertiesInDataModel, and this has been resolved.
INC-230911 · Issue 740100
Apply filter option handles passed data page reference
Resolved in Pega Version 8.8
The GetGridColUniqueValues activity was failing on step 3 when the data page reference was passed as a parameter of source report definition in a grid. This was traced to missing filter parameters for this use case and has been resolved.
INC-231721 · Issue 741742
Dataview API correctly returns value for embedded fields
Resolved in Pega Version 8.8
n QueryableDataViewTransformer, pxObjClass is populated when the payload has no embedded fields and special processing is not required. Because of pxObjClass being present, the values are parsed as per the property type and correctly populated on the clipboard and a boolean is generated correctly in the response. However, when the payload has embedded fields and special processing is required, the response body was not populated with pxObjClass and hence all fields on the clipboard were treated as strings and the data view API responded with the values in as a string irrespective of type. To resolve this, page properties have been enabled in the aggregation validator and the transformer in QueryableDataViewTransformer.java has been refactored to link the property definition.