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-193632 · Issue 679172

Cassandra driver metrics exposed for performance troubleshooting

Resolved in Pega Version 8.7.1

By default Cassandra driver metrics are now enabled. Metrics can be disabled by setting the dnode/disable_driver_metrics prconfig parameter.

INC-193847 · Issue 695974

DSS added to allow masking of subjectID in alerts

Resolved in Pega Version 8.7.1

In order to allow customizing whether or not a subjectID is included in alerts, a DSS has been added to conditionally mask the subjectID from being logged. To use this, set the "alerts/maskIHsubjectID" DSS in the Pega-DecisionEngine ruleset to true to hide the pySubjectID.

INC-194810 · Issue 691884

Removed services check and added warnings for simulations

Resolved in Pega Version 8.7.1

Attempting to run an audience simulation resulted in the error "Running simulations is not possible, because the required services are not available. Contact your system administrator to enable the data flow and real-time data grid services". Investigation showed the @DsmServices.pxHasFunctionalNodes("DataFlow","Batch") function call contained in the 'when' rule pyUnavailableDecisionServices was returning false even if all the nodes were in the cluster and all the DSM Services were in NORMAL status. To resolve this, the services check has been disabled and the simulation run will show a warning or fail if a data flow run is queued for more than 30 secs or if there is an issue with querying the underlying metrics storage.

INC-195197 · Issue 692147

Warnings added to prevent empty StrategyResult page

Resolved in Pega Version 8.7.1

When a Proposition Filter rule refers to a When rule that has "StrategyResult" declared in Pages & Classes but no "Param.StrategyResult", a design time warning will appear to indicate that this might cause discrepancy in globally optimized strategy (GOS) execution. * The warning message for a When rule with StrategyResult in Pages & Classes but not in Parameters: When rule [WhenClass: WhenName] does not have proper mapping for [StrategyResult] page. This would result in an empty [StrategyResult] page being passed into the When rule during execution. Please go to [WhenClass: WhenName] and add [StrategyResult] in the Parameters list and configure the mapping properly on Proposition Filter rule. * The warning message when StrategyResult is not in Pages & Classes but in Parameters list: When rule [WhenClass: WhenName] declares [StrategyResult] in Parameters tab, but isn't used in the conditions. This would affect performance during execution. Please remove the parameter from When rule [WhenClass: WhenName], and remove the Parameter mapping from the corresponding Proposition Filter criteria.

INC-195346 · Issue 682714

Added parser retraining for intermittent email issue

Resolved in Pega Version 8.7.1

An email listener was intermittently failing to pull the data from the email subject into the required property in the email triage case. Investigation showed that the pxEmailParser was excluding the first line in the incoming text for some cases, and has been resolved by adding code to retrain the email parser.

INC-200218 · Issue 692431

Added handling for calling truncate with external Cassandra

Resolved in Pega Version 8.7.1

A JMX exception was generated when using external Cassandra. This was traced to the combination of calling truncate and using external Cassandra for DDS, and has been resolved by adding a 'do not execute' consistency check during a truncate operation when using external Cassandra.

INC-201142 · Issue 693113

Scenario Planner performance improvements

Resolved in Pega Version 8.7.1

Scenario planner runs were causing out of memory errors on the dataflow nodes. To resolve this, updates have been made to improve performance. Only relevant information will be kept for decision funnel simulations out of SR pages, the memory footprint of data structures used to aggregate and rollup counts has been reduced, and temporary objects will be released as soon as they are not needed anymore.

INC-201216 · Issue 692415

ADM group chart level working in Prediction Studio

Resolved in Pega Version 8.7.1

Charts were not visible for Group level ADM in the Prediction Studio Models tab. This was traced to an unneeded filter for this version of Pega and has been resolved by withdrawing the filter.

INC-201340 · Issue 693021

Scenario Planner performance improvements

Resolved in Pega Version 8.7.1

Scenario planner runs were causing out of memory errors on the dataflow nodes. To resolve this, updates have been made to improve performance. Only relevant information will be kept for decision funnel simulations out of SR pages, the memory footprint of data structures used to aggregate and rollup counts has been reduced, and temporary objects will be released as soon as they are not needed anymore.

INC-201610 · Issue 691878

Removed services check and added warnings for simulations

Resolved in Pega Version 8.7.1

Attempting to run an audience simulation resulted in the error "Running simulations is not possible, because the required services are not available. Contact your system administrator to enable the data flow and real-time data grid services". Investigation showed the @DsmServices.pxHasFunctionalNodes("DataFlow","Batch") function call contained in the 'when' rule pyUnavailableDecisionServices was returning false even if all the nodes were in the cluster and all the DSM Services were in NORMAL status. To resolve this, the services check has been disabled and the simulation run will show a warning or fail if a data flow run is queued for more than 30 secs or if there is an issue with querying the underlying metrics storage.

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