Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us