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-B48902 · Issue 309982

Localization added for Marketing rulesets

Resolved in Pega Version 7.3.1

Localization has been added to decisioning rulesets in the Marketing application.

SR-B56611 · Issue 314013

Cassandra performance improved with batch query

Resolved in Pega Version 7.3.1

The data set browse by keys operation was querying Cassandra for each input record instead of using a batch query process. This has been fixed to improve performance.

SR-B56611 · Issue 315167

Cassandra performance improved with batch query

Resolved in Pega Version 7.3.1

The data set browse by keys operation was querying Cassandra for each input record instead of using a batch query process. This has been fixed to improve performance.

SR-B69727 · Issue 318519

Cassandra performance improved with batch query

Resolved in Pega Version 7.3.1

The data set browse by keys operation was querying Cassandra for each input record instead of using a batch query process. This has been fixed to improve performance.

SR-B48818 · Issue 305799

Enhancement to make Cassandra data file location configurable

Resolved in Pega Version 7.3.1

The location of the Cassandra data directory is hardcoded in versions 7.2.1 and greater and points to a different directory than previous releases. This caused problems for upgrades from pre-7.2.1 systems where disk volumes may already be configured specifically to house Cassandra data in the old locations. For Tomcat installations, the data file location is hard coded to be a directory under the Catalina Home directory. In customer systems, this creates a problem because the home directory is frequently not configured to be big enough to accommodate the Cassandra data volume. In order to improve compatibility, a new configuration property (DNode/cassandra_data_directory) has been added to override the hardcoded location using prconfig.xml, Dynamic System Settings, or the command line. Configuration options are provided for prconfig.xml and Dynamic System Settings that allow specifying the location of the Cassandra data.

SR-B45832 · Issue 308101

Application threads terminated with Pega shutdown

Resolved in Pega Version 7.3.1

The shutdown.sh command caused the actual Pega application to stop, but application threads remained running in the background. This has been updated to ensure all DSM related threads are properly shut down.

SR-B49357 · Issue 306843

Enhancement to configure multiple Cassandra instances in single rule

Resolved in Pega Version 7.3.1

To facilitate connecting multiple external Cassandra instance hosts in a connect-Cassandra rule, it is now possible to establish connection to Cassandra instances on Cassandra Connector rule form by defining multiple hosts in the field: 'eng-bigbang-perf06,eng-bigbang-perf05' using comma (,) as a separator.

SR-B49995 · Issue 308428

Proposition filter rule description updated to match decision data description changes

Resolved in Pega Version 7.3.1

Updating the description field of a proposition in the decision data did not update the description in the proposition filter rule involving that proposition as expected. This has been resolved by updating the rule which is refreshing proposition name changes to handle description change as well.

SR-B56530 · Issue 316311

Reworked destination assumptions for child dataflows

Resolved in Pega Version 7.3.1

When activating a Real time data flow run containing a Stream dataset as input which was then output to two child dataflows containing different event strategies, an IllegalArgumentException error appeared. This was traced to the pzDataFlowContainsEventStrategy activity assuming that the last shape had "Destination" in the ID in addition to an error obtaining the class. This has been fixed by properly setting the KVS type: the DataFlowRunConfig.getKeyValueStoreType() will not return NONE but default instead, and the pzDataFlowContainsEventStrategy now Iterates through all subflows and fixed secondary destination name.

SR-B69595 · Issue 317880

Fixed UnsupportedOperationException from decision table

Resolved in Pega Version 7.3.1

When using embedded properties (e.g. .OfferData.Action) within a decision table, an UnsupportedOperationException appeared on the DSMClipboardProperty if it was executed via a Strategy rule. The issue was with a function being not implemented within DSMClipboardPage, and has been fixed.

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