SR-A23395 · Issue 245032
Optimized decision data components
Resolved in Pega Version 7.2.1
Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.
SR-A23395 · Issue 243235
Optimized decision data components
Resolved in Pega Version 7.2.1
Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.
SR-A24028 · Issue 245762
Null value support added to VBD partitions SQL
Resolved in Pega Version 7.2.1
VBD partitions fail to load when facts refer to dimensions of SQL type Timestamp, Time or Date, and the dimension value is null. With the partition failing to load, inserts into those partitions hang. The code has been updated to handle null values in these areas.
SR-A24968 · Issue 247952
Performance improvements for pyComputeSegmentLogic
Resolved in Pega Version 7.2.1
Caching and updated logic have been added to the pyComputeSegmentLogic activity to improve performance.
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-A99782 · Issue 266250
XSS vulnerability closed in Warning Justification Text field
Resolved in Pega Version 7.2.2
A potential XSS vulnerability has been addressed in the Warning Justification Text field.
SR-A96515 · Issue 267504
Added handling for Qualsys security scan
Resolved in Pega Version 7.2.2
A stack overflow error was being generated when running a Qualsys vulnerability security scan on servers hosting IBM WebSphere and Pega, resulting in two of the three Pega nodes in production becoming unresponsive and requiring a restart. This was caused by the third party tool connecting to port 7003, which is used by Stream data set server, and sending unknown requests. To avoid this, the system has been updated to not send back a response if the channel is closed
SR-A79502 · Issue 253855
Corrected ability to add DNode port via prconfig
Resolved in Pega Version 7.2.2
Adding DNode Port via prconfig was not taking effect due to the configuration values being stored as strings, but the code which reads the storage port configuration treats the setting as integer. This has been fixed.
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-A102723 · Issue 270420
Pulse will not fire ADM model update until node is ready
Resolved in Pega Version 7.2.2
ADMExceptions were seen during ADM node restart due to ADM clients triggered by Pulse trying to update models on the server when the server is not yet in NORMAL state. To correct this, Pulse operation has been modified to not to fire the model update process when the node is not yet in NORMAL state.