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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-D90779 · Issue 556916

Resolved error when using IHSummary as a predictor

Resolved in Pega Version 8.4.2

After configuring the adaptive model and implementing delayed learning with IHSummary as a predictor, the exception "dataflow.StageException" appeared when the strategy was executed as part of the dataflow run. This has been resolved by implementing a cache expiry of 5 minutes.

SR-D91767 · Issue 559626

VBD planner supports URL encryption

Resolved in Pega Version 8.4.2

When using the VBD planner chart, using configure->Decision->monitoring->Visual Business Director-Datasource and then clicking on actuals generated a popup that did not have any values, and the chart was not loaded. Investigation showed that when the DSS prconfig/initialization/urlencryption/default was set to true, the Pega UI flags for encryption were not visible to code being executed by the VBD planner, resulting in the URLs not getting encrypted. To resolve this, an update has been made to set bEncryptURLs & pega.ctx.bEncryptURLs to true in VBD planner, if URL encryption is enabled.

SR-D93777 · Issue 565693

Handling added for Oracle Aggregate IH Summaries

Resolved in Pega Version 8.4.2

When using using (Non Materialized) IH Summaries to aggregate IH data, the data returned by the IH summary did not include all the expected records. If the same criteria was executed on the database via SQL or by using a strategy to process raw IH data then the results were as expected. This was due to a difference in handling of Oracle vs postgres which causes an order by clause not to be generated in the query: the postgres column name is lower case, while in Oracle it is upper case. This has been resolved by updating the system to get the column name correctly from the propertytocolumn map so IH records are returned in correct order by Browse By Keys operation.

SR-D94409 · Issue 553304

Strategy Explain message includes Component ID

Resolved in Pega Version 8.4.2

The Component ID has been restored to the Explain mode message for strategy results.

SR-D96836 · Issue 555750

Refinements made to MarkerNode memory use

Resolved in Pega Version 8.4.2

Significant memory usage can be observed when data join in strategies are missing the join conditions. E.g., when the primary source in the strategy can have up to 300 or even more propositions, the join without the join condition would perform a cartesian product with possibly up to 400 or even more records returned. This may cause performance degradation. To guard against this, an update has been made that seeks to prevent repetitive markers being accumulated under a MarkerNode while trying not to rely on any implementation of equality and hashCode for individual marker implementations.

SR-D96847 · Issue 556988

Unneeded MBean startup warning removed

Resolved in Pega Version 8.4.2

After upgrade, Catalina logs indicated the error "WARN com.pega.dsm.dnode.api.prpc.service.monitoring.MBeanDSMService - Service DataFlow doesn't implement Monitoring operation". This was due to a flaw in the way the data flow DSM service was initialized in client mode. The exception itself was not a problem and did not impact functionality, but the client initialization has been modified to remove the warning.

INC-126556 · Issue 564032

Declaratives disabled during startup

Resolved in Pega Version 8.4.2

Declaratives firing before the engine is fully up can lead to null pointer errors. In order to avoid this condition, declaratives will be disabled during startup so that unnecessary operations can be avoided and system can be started faster.

SR-D16934 · Issue 493702

External Cassandra nodes listed in DDS cluster

Resolved in Pega Version 8.3.1

Nodes of an external Cassandra cluster were not listed in the DDS cluster except for the first one in the host list, and when the “only” listed Cassandra node was restarted, the status on the DDS cluster LP did not become “NORMAL” afterwards. In addition, even though other C* nodes were up and running, the external Cassandra cluster was reported as unreachable. This was an unintended side effect of work done on the landing page to reflect the real state of the nodes after some were killed and restarted, and has been corrected by refining the equals() and hashCode() methods for DDS member info in order to better differentiate the external Cassandra nodes.

SR-D22686 · Issue 493516

IH summaries working with external Cassandra

Resolved in Pega Version 8.3.1

Summaries were not working for external Cassandra. This was an issue with the IH summary component using the aggregated dataset as a reference, and this fix contains several components to improve this function. An issue where the IH aggregates dataset does not materialize when DDS is external Cassandra has been resolved by modifying the code that checks the DDS availability. A filter that was used to match “” did not work when pre-aggregation is off : this was due to the IH Browse operation being done outside of a DF context, and has been fixed. The IH Summary shape not working properly in a strategy if it referenced an aggregate dataset with pxInteractionID as part of the group-by properties was traced to an issue with it generating a pxInteractionID value when executing the strategy, and has been resolved by excluding pxInteractionID from the group keys in the IH Summary shape.

SR-D24880 · Issue 494171

CEP bucket size increased to 1 minute

Resolved in Pega Version 8.3.1

Frequent DSM Data Flow Errors were observed in production nodes with very high event rates. This was traced to the default bucket size for CEP being 1 second for a 31 day window, which was not sufficient to handle high volume use which may create an event strategy window large enough to hit the Cassandra column size limit. In order to resolve this, the default bucket size has been increased from 1 second to 1 minute.

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