SR-A13157 · Issue 224896
Performance enhancements in DSM
Resolved in Pega Version 7.2
Performance enhancements have been made to DSM. These include improving the timing info for Switch, Champion Challenger, Exclusion, and Data Join, and adding a Smart clone feature of SR pages if a check indicates that cloning would minimize memory footprint.
SR-A10575 · Issue 220506
DSM monitoring and troubleshooting enhancements
Resolved in Pega Version 7.2
Monitoring and troubleshooting improvements have been made to the DSM components D-Node, VBD and ADM. These include an HTTP call which returns a node status that can be integrated into monitoring tools and raise appropriate alerts, and services to provide diagnostics information about d-nodes that can be sent by the cloud team to engineers for troubleshooting.
SR-A10575 · Issue 221174
DSM monitoring and troubleshooting enhancements
Resolved in Pega Version 7.2
Monitoring and troubleshooting improvements have been made to the DSM components D-Node, VBD and ADM. These include an HTTP call which returns a node status that can be integrated into monitoring tools and raise appropriate alerts, and services to provide diagnostics information about d-nodes that can be sent by the cloud team to engineers for troubleshooting.
SR-A6903 · Issue 216455
Data Flow correctly handles table encountering null numeric columns
Resolved in Pega Version 7.2
When a data set was created on top of a exposed table which contains some null value in numeric columns, a Data flow executed using that data set used the value '0' instead of the expected null property. This was traced to the Data Flow batch run execution using the DSMClipboardPages, which weren't able to differentiate if a property was present or not and led to null being mapped to 0 in a numeric property. To correct this, the NativeSQLAPI will return null values as empty values when querying a DB and will not use them populate a DSM page or propagate them in the data flow.
SR-A6903 · Issue 216454
Data Flow correctly handles table encountering null numeric columns
Resolved in Pega Version 7.2
When a data set was created on top of a exposed table which contains some null value in numeric columns, a Data flow executed using that data set used the value '0' instead of the expected null property. This was traced to the Data Flow batch run execution using the DSMClipboardPages, which weren't able to differentiate if a property was present or not and led to null being mapped to 0 in a numeric property. To correct this, the NativeSQLAPI will return null values as empty values when querying a DB and will not use them populate a DSM page or propagate them in the data flow.
SR-A7401 · Issue 216480
Performance tune-ups in DSM
Resolved in Pega Version 7.2
Strategy Profiler was showing misleading timing information for Switch, Champion Challenger, Exclusion, and Data Join. This has been fixed. In addition, Strategy Set has been optimized to let it evaluate the customer-specific expressions once per component execution (instead of per SR page) , and it will not clone SR pages if it's unnecessary. The Prioritization shape has also been improved to only prioritize the Top N if that?s configured.
SR-A7401 · Issue 219542
Performance tune-ups in DSM
Resolved in Pega Version 7.2
Strategy Profiler was showing misleading timing information for Switch, Champion Challenger, Exclusion, and Data Join. This has been fixed. In addition, Strategy Set has been optimized to let it evaluate the customer-specific expressions once per component execution (instead of per SR page) , and it will not clone SR pages if it's unnecessary. The Prioritization shape has also been improved to only prioritize the Top N if that?s configured.
SR-A12733 · Issue 227212
Fixed NPE for Tracer
Resolved in Pega Version 7.2
It was not possible to execute strategies if the tracer was turned on. This was failing because the tracer was trying to collect the primary page in XML format from a clipboard page that was missing the implementation to generate the XML. This has been corrected.
SR-A13237 · Issue 227844
Fixed NPE for Tracer
Resolved in Pega Version 7.2
It was not possible to execute strategies if the tracer was turned on. This was failing because the tracer was trying to collect the primary page in XML format from a clipboard page that was missing the implementation to generate the XML. This has been corrected.
SR-A12341 · Issue 226423
Corrected implementation for DataFlow key non-match
Resolved in Pega Version 7.2
If a DataFlow Dataset configured against a Report Definition had a property key name that was not identical to the column name in the database table, the Dataflow failed to execute with error " Incorrect implementation for Report Definition as a data flow source. Property-to-database table column mapping was not applied correctly". The implementation has been fixed to resolve this issue.