SR-D26976 · Issue 507215
Filter added to ensure correct context for proposition strategy rules
Resolved in Pega Version 8.1.7
Given two applications (ex App1 and App2) hosted on the same domain where App2 was built on App1, trying to create a strategy rule in App1 and do a test run strategy using the propositional data component which internally uses App2 propositions generated the error: Failed to find a 'RULE-DECISION-DECISIONPARAMETERS' with the name 'GROUP_2'. There were 1 rules with this name in the rulebase, but none matched this request." Investigation showed the strategy was using the PropositionNoCacheUtils and PropositionTools java classes to load the propositions during run time. In these classes, the group classes were browsed from the db irrespective of the application context, causing the strategy run to fail as it was not able to access the decision data rules in other applications which shared the same SR class as the current application. To resolve this, a filter has been added to the PropositionNoCacheUtils and PropositionTools java classes to filter out the groups that are not in the current application context.
SR-D31103 · Issue 502980
VBD insert process updated for better retry handling
Resolved in Pega Version 8.1.7
When restarting Data Flow and VBD nodes, the VBD client can encounter some exceptions indicating components in the stack are temporarily unavailable. In most cases the VBD client retries, but there are some cases where it did not and data flow failures occurred. To resolve this, the code has been updated to remove logging of the VBD cluster status during a retry, and the retry duration has been made configurable.
SR-D37163 · Issue 505479
Corrected Decision Data import filter behavior
Resolved in Pega Version 8.1.7
After upgrade, if a Decision data import referred another component to filter out the import, it did not work. This has been corrected.
SR-D38492 · Issue 505491
Batching now enabled when using IH Summary shape in substrategies
Resolved in Pega Version 8.1.7
Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected.
SR-D39956 · Issue 511639
Corrected method IF use with shortcut function
Resolved in Pega Version 8.1.7
After upgrade, method IF was not working as expected when used in an expression like "@if(.totalorders_120days>0,(.remakeorders_120days/.totalorders_120days)<0.3,false)". This was caused by a missed use case for the combination of an exception-generating function in combination with a shortcut function (i.e. ternary, and, or), and has been resolved.
SR-D47713 · Issue 511972
Corrected issue with strategy framework testing
Resolved in Pega Version 8.1.7
Issues were seen in creating a dataflow to test the strategy framework shipped with the Pega Marketing product. It was not possible to use a data transform to test this strategy because it is in the shipped PegaMKTEngine ruleset. Investigation showed the value of appliedToClass was retrieved from "pyRunOnDataFlowClassName" instead of from the running strategy, and this has been resolved.
SR-B52067 · Issue 311178
Handling improved for extremely large data flow run statistics page
Resolved in Pega Version 7.3.1
A data flow monitoring page with 1000+ data flow shapes in total was hanging while loading the statistics. This happened because the component statistics table had no pagination enabled, and displaying all 1000+ shapes in one screen caused the browser to hang. This has been remedied with: - Pagination on the component statistics table in the data flow monitoring screen - Filtering on the component statics table, allowing monitoring of only relevant data flow components
SR-B69080 · Issue 318226
Local PegaAPI instance added for Monte-Carlo dataset
Resolved in Pega Version 7.3.1
A dataflow running from a Monte-Carlo data set was failing due to stale thread exception. This was due to the PegaAPI variable 'pega' not being defined as local variable in the Montecarlo dataset generator, and has been resolved by creating a local variable PegaAPI instance.
SR-B53147 · Issue 310299
HDFS configuration updated to support KMS server
Resolved in Pega Version 7.3.1
A field has been added in HDFS configuration to allow configuration of a KMS server. This setting will be propagated to all places where Hadoop configuration is used - hdfs & parquet data sets.
SR-B74689 · Issue 324632
Marketing data flow run made more robust
Resolved in Pega Version 7.3.1
After upgrade, it was observed that Pega Marketing Campaigns were failing if there were no customers in the Audience configured on the Campaign, generating the error message "The run failed, because it exceeds the maximum number of failed records, which is currently set to 0". The cause of this was executing a distributed data flow with a database as primary source on an empty table, leading the run to fail as a table without any partition was considered in the handling. The database dataset has now been updated to differentiate the case when there's no partition available from the case when there's a single partition for every record, ensuring the DB data set now returns 'all' records when there is no partition key defined, and the data flow handles the no values for partitions in a more robust way.