SR-A21844 · Issue 241153
VBD enhancements
Resolved in Pega Version 7.2.1
The following enhancements have been added to the Visual Business Director feature of PRPC Decisioning: - Support added for changes in field sizes after partitions load - Partitions will be loaded immediately on VBD server startup - Data expiration based on inactivity is disabled to reduce query latency - Timeout added to VBD queries to handle latency when Partitions initially load - Code that processed Actuals query JDBC resultset is optimized
SR-A22841 · Issue 245073
All Data Flow keys considered for filtering
Resolved in Pega Version 7.2.1
When a Data Flow containing a Filter was run , the filter step showed incorrect results in the "Successful records" column even though previewing it from the Data Flow rule it showed the correct result. The algorithm that queries a secondary source shape in the data flow was ignoring all but the first key, and has been updated to properly process all of the keys before displaying any results.
SR-A23035 · Issue 245109
Enabled bulk delete of ADM models
Resolved in Pega Version 7.2.1
In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria." PLEASE NOTE: activity is not constrained by Application, only by the criteria provided as parameters. Therefore in most cases you will probably want to constrain by 'applies to' class in addition to the other criteria. Please see the tooltip / description of each parameter for more info on their usage. Integer output parameter 'NumberDeleted' returns the number of models that were successfully deleted."
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