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.

SR-C66639 · Issue 406175

Localization added to "Text" in Themes page

Resolved in Pega Version 8.2

The header "Text" in the Themes page was not localized properly due to the field value created in the wrong applies-to class . There is a field value in @baseclass but is in Pega- DecisionArchitect ruleset might not have been considered while exporting rules for translation . Will create another one in @baseclass /Pega-EndUserUI

SR-C50284 · Issue 390659

Top level activity steps are numbered correctly when child steps exist

Resolved in Pega Version 8.2

Top level activity steps were showing as being numbered incorrectly when child steps existed, but saving the rule or refreshing the rule corrected the numbering. This was caused by CSS that was added to the rule form harness to increment the step number; while expanding a top level node the reset happened and then the counter initialized the value. To address this, the code has been changed from CSS counter to CSS attr which will use the index attribute of the current row. Additional CSS cleanups were also done to remove IE9 and other browser-specific styling that is no longer needed.

SR-C48056 · Issue 391569

RRChartDiv tries resize three times before exiting to prevent high CPU usage

Resolved in Pega Version 8.2

Very high CPU usage was reported when two or more tabs were open, even when there was not actual work being performed in the app. This was traced to a chart in Team Dashboard that was displayed with "No data to display"; because the toolbar height was always 0, the resize callback was going into an infinite loop. This has been fixed by modifying the logic in pzRRChartDiv to only try the resize three times to get the height of toolbar or slider before exiting.

SR-C50381 · Issue 391849

Save Parameters checkbox in Marketing AssociationCategory now disabled by default to resolve exception during campaign

Resolved in Pega Version 8.2

An exception was thrown in the logs if an access group had any categories added or deleted while running a campaign in the marketing framework. This was traced to the checkbox "Save parameters with this property for access on reopen" being enabled by default, which ended up adding empty category tags to the Access Group Rule while running. This checkbox in pyAssociationCategory property has now been unchecked by default.

SR-C53967 · Issue 392506

New wrapper API created to handle external Cassandra nodes for ADM models

Resolved in Pega Version 8.2

When the Decision Data Store Service was configured to use an external Cassandra instance, the Adaptive Models Management landing page did not list the number of models when a strategy referencing an ADP Model was run, and the message "Error loading adaptive decision management server data. Ensure adaptive decision manager and decision data store service nodes are available." was displayed. This issue was traced to the ADM service relying on a FunctionalNodes API provided by DSM service infrastructure that was not able to recognize external Cassandra nodes. To correct this, a new wrapper API pyADMHasFunctionalNode has been created.

SR-C53999 · Issue 393425

Added missing validation trigger for survey question page

Resolved in Pega Version 8.2

Validate rule or preaction was not firing as expected for the Question page in Pega Survey. This was due to a missing step which has now been added to pzDisplayQuestionPagePostAct.

SR-C49844 · Issue 394996

Added check for external Cassandra cluster to avoid unnecessary DDS pulse error logging

Resolved in Pega Version 8.2

After upgrade, DDS pulse errors were filling up the jvm.out logs. This was caused by a check in system_auth keyspace that was redundant for sites running their own Cassandra cluster (external). To fix this, DDS pulse operation will check If the Cassandra cluster is external; if it is, it will not check system_auth keyspace and will Omit DDS pulse operation actions except update logging.

SR-C57025 · Issue 395184

Filter value Autocomplete uses localized text for the 'Case Type' string

Resolved in Pega Version 8.2

The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.

SR-C40145 · Issue 392708

Restarting the SVM training analysis checks for existing model request to continue

Resolved in Pega Version 8.2

When creating a predictive model there was an issue with completing the SVM training analysis either due to error or browser crash. In previous versions of Designer Studio the session would stay alive and continue to execute, however more recent versions of the decision analysis's portal expected the user to keep the session active in order for the model to complete even though for long-running model training it is not viable to keep a session open for many hours. This was caused by the model generation process being kicked off again when the wizard was relaunched, and has been resolved by adding a check to the relaunch that will look for an existing model generation request and continue with the same request if one is found.

SR-C58241 · Issue 402735

Agent Access Group corruption resolved

Resolved in Pega Version 8.2

The Access Group used by agents was intermittently becoming corrupted. This was caused by a timing issue where sometimes the conclusion was built before the rulesets to the requestor were set up, resulting in the role being added to the RoleNotFound cache. To resolve this, the RoleNotFound cache has been removed so that every time a role lookup happens the system will check the database.

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