Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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.

INC-174661 · Issue 678823

Handling added for clearing node killed between assignment and processing

Resolved in Pega Version 8.6.3

An Offer flow was not resuming after it expired according to the wait shape. Investigation traced this to partitions which were assigned to a dead node in NEW state where they were not picked up by the dataflow. The problem was only encountered in the unusual situation when a dataflow node was killed in the brief period of time between the assignment and the processing, and has been resolved by adding an update which will clear unknown new assigned partitions for the batch run health task.

INC-179879 · Issue 664804

Localization added to DelegateDescription

Resolved in Pega Version 8.6.3

Localization was not working correctly for the description of a delegated rule due to pyDelegeteDescription being defined with a non-localized Property value. This has been resolved by localizing the property value for pyDelegeteDescription.

INC-183211 · Issue 667011

Compare-To-Empty-String support added to Analyzer

Resolved in Pega Version 8.6.3

An enhancement has been added to support a NotEquals decision function in the Analyzer.

INC-186437 · Issue 685013

Updated entity attachment extraction tokenizers

Resolved in Pega Version 8.6.3

After creating an entity extraction model, it was seen that one of the entities worked when there was a space after the semicolon but the detection was not working if there was no space. This has been resolved by updating the Tokenizers with extra examples to address tokenization when ":" is present between two words without any spaces.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us