SR-B64710 · Issue 317013
Revision management browse refined to handle multiple applications
Resolved in Pega Version 7.3.1
If an instance had two applications with respective overlays, the rollback of a revision in one application was using the revision from the other application instead of fetching the revision list from the active application. In order to support this structure, the browse condition in pyCreateRevisionVersion has been reworked to browse the activated revisions and pick the latest activated revision to make it active from inactive, then make the current revision as rolled back.
SR-B66424 · Issue 315782
Backwards compatibility added for Stream datasets
Resolved in Pega Version 7.3.1
In order to ensure backwards compatibility for the Data-Admin-DataSet-Stream property pyKeys (formerly pyPartitionKeys), logic has been added to handle stream datasets created in previous releases: if pyKeys (the new property) is empty and pyPartitionKeys (the deprecated property) is not empty, then pyPartitionKeys will be used.
SR-B56514 · Issue 313700
Enhancement to support high number of Adaptive Model predictors
Resolved in Pega Version 7.3.1
It was not possible to save an adaptive model rule with more than approximately 650 predictors. This was a long-standing issue with JVM per-method limits relating to how the rule code for Adaptive Model predictors was generated, but an enhancement has been added to modify the Java rule generation so it will not try to find values for all the predictors in one method and support more complex use.
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.