SR-A96852 · Issue 264159
Resolved OOM error when adding VDB DNode
Resolved in Pega Version 7.2.2
A memory leak was found relating to JBDC PreparedStatement objects (char arrays allocated to hold database query results) used when VBD loads its data partitions. This has been fixed with the addition of code to close the PreparedStatement objects created when loading Actuals partition data.
SR-A88481 · Issue 256518
VBS starts with DDS configured to use external Cassandra
Resolved in Pega Version 7.2.2
If DDS is configured with Internal Cassandra which is then switched to External, DDS reports to be in state NORMAL and VBD can start. However, when starting from scratch with DDS configured to use External Cassandra, DDS was failing validation and reporting to be in state CLIENT, so VBD was unable to start due to VBD's check that ensures at least one DDS is in the NORMAL state before starting. To address this, the validation code that checks the DDS state when VBD is starting has been removed and the system will instead rely on the DSM service layer to ensure that DDS is functional before VBD can start.
SR-A90821 · Issue 258447
Delayed Learning data flows use dynamic objects
Resolved in Pega Version 7.2.2
Data flows with delayed learning enabled were failing to run when initiated by a campaign. The root cause for this bug was the process where a data flow object was created only once and the same object was shared between multiple data flow runs in the node. The changes for this fix include making the DataFlow object non-static in the DelayedLearning.java class.
INC-142084 · Issue 599876
Support added for expression in strategy scorecards
Resolved in Pega Version 8.2.8
When invoking REST against a dataflow that had a strategy containing a scorecard that used an expression and the "Include model explanations option" was enabled in the Strategy configuration, the system failed with the error "PropertyValueInvalid .pxMaxScore Cannot cast the value (unknown) to double". This was traced to the Scorecard explanations failing during serialization when an expression was used, and has been corrected.
SR-A24962 · Issue 250080
DataSet-Execute updated to correct time-to-live error
Resolved in Pega Version 7.2.2
When using the time to live option of a Decision Data Store dataset, the java generation for the DataSet-Execute method was causing java compilation errors. This was due to an inconsistency between the code generation for DataSet-Execute method in an activity and the settings provided. To correct this, the algorithm used to generate the code for DataSet-Execute method has been updated to include the time to live setting and to generate correct and compilable code.
SR-A24962 · Issue 248678
DataSet-Execute updated to correct time-to-live error
Resolved in Pega Version 7.2.2
When using the time to live option of a Decision Data Store dataset, the java generation for the DataSet-Execute method was causing java compilation errors. This was due to an inconsistency between the code generation for DataSet-Execute method in an activity and the settings provided. To correct this, the algorithm used to generate the code for DataSet-Execute method has been updated to include the time to live setting and to generate correct and compilable code.
INC-130761 · Issue 570061
ADMSnapshot agent defaults to running on a single node
Resolved in Pega Version 8.2.8
The ADMSnapshot agent runs when ADM is used, and should be run on only one node to prevent duplicate snapshots being created. To ensure preferred behavior, the "Run this agent on only one node at a time" option has been selected by default for ADMSnapshot agent.
SR-D93777 · Issue 565692
Handling added for Oracle Aggregate IH Summaries
Resolved in Pega Version 8.2.8
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-A87150 · Issue 256602
Dynamic setting added to override ADM JMS default
Resolved in Pega Version 7.2.2
ADM (a part of Pega DSM) was detecting JMS and switching over to JMS when available and using HttpInvoker in other cases. In order to allow customization, it is now possible to override the ADM JMS configuration and allow EAR deployments by way of a dynamic system setting to disable JMS at will.
SR-A80606 · Issue 254964
Data Import API updated to be case-sensitive
Resolved in Pega Version 7.2.2
When using a Data Import Shape for a Class Type which had a same named property identifier (but with a different case) as in the SR hierarchy, both the properties were considered valid and imported as SR properties. This caused issues in the strategy rule as the Set property components set the values for the incorrect instance and eventually led to strategy failures as the expected instance did not have a value set. This has been resolved by using a case-sensitive API to validate the source property against the target class.