SR-D38492 · Issue 505488
Batching now enabled when using IH Summary shape in substrategies
Resolved in Pega Version 8.3.1
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 511636
Corrected method IF use with shortcut function
Resolved in Pega Version 8.3.1
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-D37945 · Issue 506798
Server node cache refresh will use remote execution timeout
Resolved in Pega Version 8.3.1
A campaign was failing due to VBD remote ping timeout with a stacktrace that indicated a StageException. Investigation showed that when the cluster is heavily loaded, calls to the remote execution API could time out. If this occurred when the VBD client was refreshing its cache of VBD server nodes, then the insert failed and the error was propagated up the calling data flow. To resolve this, the system will use the remote execution timeout when refreshing node cache, extend the timeout to 60 seconds, and ensure timeouts are retried during inserts.
SR-D22686 · Issue 493516
IH summaries working with external Cassandra
Resolved in Pega Version 8.3.1
Summaries were not working for external Cassandra. This was an issue with the IH summary component using the aggregated dataset as a reference, and this fix contains several components to improve this function. An issue where the IH aggregates dataset does not materialize when DDS is external Cassandra has been resolved by modifying the code that checks the DDS availability. A filter that was used to match “” did not work when pre-aggregation is off : this was due to the IH Browse operation being done outside of a DF context, and has been fixed. The IH Summary shape not working properly in a strategy if it referenced an aggregate dataset with pxInteractionID as part of the group-by properties was traced to an issue with it generating a pxInteractionID value when executing the strategy, and has been resolved by excluding pxInteractionID from the group keys in the IH Summary shape.
SR-A20073 · Issue 238485
Corrected runtime handling for List Utility functions inside strategies
Resolved in Pega Version 7.2.1
When the List Utility functions 'IsInPageListWhen' and 'IndexOfPageList' were used inside strategies, the functions worked in the API(webservice) request but generated UnsupportedOperationException errors in the Program run. This was traced to a missing implementation of DSMClipboardProperty.indexOf(), which has now been added.
SR-A20073 · Issue 235672
Corrected runtime handling for List Utility functions inside strategies
Resolved in Pega Version 7.2.1
When the List Utility functions 'IsInPageListWhen' and 'IndexOfPageList' were used inside strategies, the functions worked in the API(webservice) request but generated UnsupportedOperationException errors in the Program run. This was traced to a missing implementation of DSMClipboardProperty.indexOf(), which has now been added.
SR-D22686 · Issue 496861
Added DSS to handle BIX extracts under parse delimiter rules
Resolved in Pega Version 8.3.1
When parse delimiter rules were applied, the File Listener was not parsing the CSV manifest file generated from a BIX extract until the file was resaved. This was traced to a space after a comma in the extracted files, and has been resolved with the addition of a DSS which enables the use-specified delimiter to remove the space after the comma in the manifest files.
SR-D41616 · Issue 509808
Corrected Cassandra startup error related to client authentication
Resolved in Pega Version 8.3.1
During provisioning, Cassandra nodes in PegaDDSTier failed to join the cluster and the error "Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered during startup: Invalid yaml. Those properties [truststore_password, truststore] are not valid" was generated. Investigation showed that the recent addition of support for client authentication using the settings "dnode/cassandra_client_encryption/truststore" and "dnode/cassandra_client_encryption/truststore_password" resulted in nulls being set cassandra.yaml if the new parameters were not given values. To resolve this, truststore and truststore_password will not be added to cassandra.yaml when they are not set in prconfig or system settings.
SR-A18333 · Issue 237135
Corrected JSON page group handling
Resolved in Pega Version 7.2.1
If DataSet-Execute method was used to cache a CustomerPage from Clipboard, using the same DataSet-Execute method to retrieve it from the cache using the "Browse by key" operation was not working correctly: If the page contained a page group property, then the retrieved CustomerPage contained additional invalid entries that led to errors in the mapping logic. This was an issue with the Clipboard page JSON converter not properly handling page groups, and has been corrected.
SR-D26976 · Issue 507216
Filter added to ensure correct context for proposition strategy rules
Resolved in Pega Version 8.3.1
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.