SR-A11148 · Issue 222428
Elastic Search updated for external tables
Resolved in Pega Version 7.2
Elastic Search on an external table was returning incorrectly limited results. This was an issue with passing more than one property set in the query to the external table, and has been resolved by updating AbstractIndexer to add additional properties.
SR-A11148 · Issue 221666
Elastic Search updated for external tables
Resolved in Pega Version 7.2
Elastic Search on an external table was returning incorrectly limited results. This was an issue with passing more than one property set in the query to the external table, and has been resolved by updating AbstractIndexer to add additional properties.
SR-A2733 · Issue 221219
Migration process handles underlying varchar CHAR
Resolved in Pega Version 7.2
Handling for CHAR length semantics has been added for imports of rule schema to support Oracle varchar2 columns, and the import/export will correctly deal with the circumstanced columns of CASETYPEVERSION and PXREFOBJECTCLASS.
SR-A11286 · Issue 224545
Drop Index SQL updated to remove duplicates
Resolved in Pega Version 7.2
If a query was used in SchemaManager to get all of the covered indexes for the table, firing the same query in the DB to generate XML resulted in duplicate indexes and column names. This was traced to the Drop Index SQL being generated twice, and the query to get the covered index columns from the DB has been changed to remove the duplicates.
SR-A11286 · Issue 223221
Drop Index SQL updated to remove duplicates
Resolved in Pega Version 7.2
If a query was used in SchemaManager to get all of the covered indexes for the table, firing the same query in the DB to generate XML resulted in duplicate indexes and column names. This was traced to the Drop Index SQL being generated twice, and the query to get the covered index columns from the DB has been changed to remove the duplicates.
SR-A6547 · Issue 217014
Updated handling for empty keys in DataSet-Execute
Resolved in Pega Version 7.2
When executing a 'delete by keys' operation in a DataSet-Execute method, passing empty keys would intermittently cause the whole dataset to be truncated or deleted. To create a more robust execution environment, when a Dataset-Execute is called and no key is passed it will trigger a delete statement matching the key value to null.
SR-A6629 · Issue 216162
Updated group authentication for populating Batch Processing landing page
Resolved in Pega Version 7.2
pyApplication and pyApplicationVersion were not getting populated when running a data flow from the Batch Processing landing page that used information from system pages. This was an issue with the system pages not being included in the proper authentication group, and has been resolved.
SR-A8103 · Issue 216452
DSM thread CPU consumption resolved
Resolved in Pega Version 7.2
In certain installations, a DSM thread that was not properly sleeping after the system was upgraded caused degraded performance. This has been corrected.
SR-A8236 · Issue 217418
Removed default overriding threads per node setting of Topology page
Resolved in Pega Version 7.2
The number of threads per node specified in Decision->Simulation Settings->Topology landing page was not being taken into account by the data flow execution, leading to the inability to configure vertical scalability per PRPC node and/or exclude certain nodes from data flow execution. This was traced to a default value overriding the setting from this page, and the code has been updated to correctly reflect the setting being used.
SR-A8099 · Issue 216453
Null/empty values removed from propagation instead of being set to 0
Resolved in Pega Version 7.2
Numeric properties without a value set were being propagated as value 0 during data flow execution. This was due to a clipboard page error in the Data Flow batch run execution, and this has now been updated to to ensure null or empty properties will not be propagated in the data flow.