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-143121 · Issue 610735
Timeout for loading predictors made configurable
Resolved in Pega Version 8.5.3
When using an extremely large number of predictors, the Report definition pzADMPredictorsFilter was suffering timeouts due to the time for loading predictors from the database exceeding the time threshold allowed. This has been resolved by marking the rule as editable to allow custom setting of the threshold according to need.
INC-150395 · Issue 625070
Tokenizer updated to handle commas
Resolved in Pega Version 8.5.3
The Text Analyzer was not working as expected in cases where the number was combined with a comma (,) with it but was working when a space was used between the number and the comma. This was traced to the tokenizer not correctly processing and splitting the input text when there was a special character before or after the token. This has been resolved by updating the tokenizer logic.
INC-150873 · Issue 612897
Performance improvement for saving ADM model rule
Resolved in Pega Version 8.5.3
Saving an ADM model rule generated a heap dump. The stack trace from the heap dump showed a thread consuming the maximum memory (4.7 GB of memory). Configurations on all factories are updated when a model rule is saved, but at the time of development it was not expected that there would be a lot of factories in a Dev environment so the system was loading all existing factories simultaneously into memory and updating configurations on them. To improve performance, an update has been made which will now sequentially load factories and update the configuration.