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.
INC-126129 · Issue 569666
PropertyToColumnMap made more robust
Resolved in Pega Version 8.1.9
The DF_ProcessEmails dataflow was intermittently failing with a StageException error. This was traced to schema changes being propagated asynchronously by system pulse, which seem to have caused PropertyToColumnMap to cache stale schema. To resolve this, if the property mapping is not found the first time, the system will make a second attempt to get the mapping. Additional logging has also been added for better diagnostics.
INC-128385 · Issue 564521
Behavior made consistent between SSA and legacy engines
Resolved in Pega Version 8.1.9
There was a behavioral disparity between the legacy execution engine and the SSA engine where the latter was not creating a new page when the index was one above the size of the page list. This has now been corrected in order to make the SSA behavior fully backward compatible with the legacy engine, i.e. a new blank page will be added to the list if the index is one above the size of the list.
INC-129222 · Issue 568530
Handling improvements for commit logs
Resolved in Pega Version 8.1.9
The ADM commit log logs the number of unconsumed messages that are going to expire. In certain circumstances, it can include unconsumed messages that are not going to expire in the count. Because they are not expired and removed, the environment was running out of disk space due to the ADM commitlogs table growing larger than expected and performance issues were seen. To resolve this, a new adm_commitlog.adm_responses_commit_log_date_tiered table has been created, with a default_time_to_live of 24 hours. DateTieredCompactionStrategy has been set with max_window_size_seconds as 24hrs and tombstone_compaction_interval as 24hrs.