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-219186 · Issue 720470

Prefix allowed for aggregates Keyspace

Resolved in Pega Version 8.6.5

Attempting to connect multiple Pega environments to an external Cassandra cluster with limited database access using the prconfig setting dnode/keyspaces_prefix resulted in the error "Unable to determine if cassandra table [aggregates.config] exists" while connecting to the aggregates Keyspace. This was traced to an incomplete implementation: the system allowed the keyspace to be created with the prefix, but queries used the keyspace name without the prefix. In order to support this use, an update has been made to ensure keyspace prefixes are used if present.

INC-220174 · Issue 716384

Improved cleanup for data from joining nodes

Resolved in Pega Version 8.6.5

A Cassandra node that is down for longer than the grace period (default 10 days) can introduce zombie data that creates instability when it returns to the cluster. This can include VBD partition summary data that was deleted and can break loading rules and cause the service to fail to start up. To resolve this, additional logic has been implemented to detect zombie summary records, including summary records without field descriptors and summary records without dictionaries having already been provided, and to read dictionaries from the latest summary record in case there are preceding zombie records with dictionaries.

INC-222561 · Issue 721043

Check added for destination type for distribution test reports

Resolved in Pega Version 8.6.5

When there were two output destinations in the system, one of type VBD and another of type Database table and both had the same name, an incorrect class was set for distribution test reports and an error was generated when trying to open the report. Investigation showed the system was only checking for the name of the destination and not its type; this has been resolved by adding a pzSetSimulationOutputClass data transform to check for the destination type in addition to the destination name when setting the class for reports.

INC-224038 · Issue 723258

Performance improvement for serviceregistry table queries

Resolved in Pega Version 8.6.5

The expression filter ($1 - "SSR"."pytimeout") in the queries for service registry table caused full table scans which might result in performance issue and even risk of contention/locking. This has been resolved by replacing the pyTimeout column reference in filters to the default value = 9000ms so that performance for these queries can be improved.

INC-205666 · Issue 702934

Database table correctly prevents deletion if there are descendant classes

Resolved in Pega Version 8.6.5

When deleting a concrete class with descendant classes via an activity (Rule-.Delete), the Rule-Obj-Class.ValidateDeleteInternal activity was throwing an error message indicating the class could not be deleted due to descendant classes. However, the corresponding database table rule was deleted anyway. Investigation showed this was caused by ValidateDeleteInternal not reaching the Obj-Save-Cancel step. This can be fixed by modifying step 11, the post when conditions, to jump to END and set the END label at the Obj-Save-Cancel step instead Exit-Activity, but this issues has been resolved by updating all failure states to run end step. In addition, security has been updated to disallow "Allow invocation from browser".

INC-205938 · Issue 721200

Improved handling for heavy use of PushDailyUserData

Resolved in Pega Version 8.6.5

The PushDailyUserData agent was causing utility node performance issues due to the amount of data it was fetching from pr_hourly table. To resolve this, an update has been made which will run the agent once per day and chunk large data.

INC-209158 · Issue 722412

Loop handling updated for Decision Table OR conditions

Resolved in Pega Version 8.6.5

The system was crashing when saving or checking in a decision table with 21 columns and 20 rows where each cell contained 1, 2, or 3 OR conditions. Investigation showed this was caused by an indefinite number of loops when 'or' conditions were used in the test consistency activity, and this has been resolved with an update which ensures only the specified number of loops are performed.

INC-211248 · Issue 713158

Survey navigation type set for use with complex CB refresh

Resolved in Pega Version 8.6.5

After upgrade from Pega 7.1 to Pega 8.5, creating a legacy survey used in pxSurveySection with a complex CB question page that contained a refresh option had collapsed tree navigation, the survey name was blank, and duplicate labels were found in picklist questions. To resolve this, an update has been added which will set the navigation type in parameters after a complex CB refresh and skip page copy while upgrading survey work objects.

INC-213918 · Issue 714454

Discard button works consistently

Resolved in Pega Version 8.6.5

After check out, the discard button was not working consistently for decision tables or MapValue. Investigation showed this occurred when an exported file was being downloaded in the same window, as the thread would be busy with the file and not able to perform the discard action on the window. To resolve this, the configuration for the download on the same window has been removed, exportToDecisionTable has been modified to handle an iframe, and a runScript action has been added to register the exportToExcel activity and download in iframe.

INC-215785 · Issue 722553

Corrected logic for parsing imported Excel formula cells

Resolved in Pega Version 8.6.5

Integers specified as cells with formulas in Excel were getting an additional ".0" in them due to them being parsed internally as doubles during the floating point arithmetic of the Apache POI library. This has been resolved by modifying the logic in ExcelUtils.java to apply DataFormatter to get the string value instead of an integer by default for a formula cell.

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