INC-213918 · Issue 714452
Discard button works consistently
Resolved in Pega Version 8.7.2
After check out, the discard button was not working consistently for decision tables or MapValue. Investigation showed this occurred when an exported file was being downloaded in the same window, as the thread would be busy with the file and not able to perform the discard action on the window. To resolve this, the configuration for the download on the same window has been removed, exportToDecisionTable has been modified to handle an iframe, and a runScript action has been added to register the exportToExcel activity and download in iframe.
INC-213918 · Issue 714453
Discard button works consistently
Resolved in Pega Version 8.8
After check out, the discard button was not working consistently for decision tables or MapValue. Investigation showed this occurred when an exported file was being downloaded in the same window, as the thread would be busy with the file and not able to perform the discard action on the window. To resolve this, the configuration for the download on the same window has been removed, exportToDecisionTable has been modified to handle an iframe, and a runScript action has been added to register the exportToExcel activity and download in iframe.
INC-132590 · Issue 590493
Exported Excel from Decision Table wraps correctly
Resolved in Pega Version 8.6
After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).
INC-160437 · Issue 629645
Upgrade compatibility enhanced for Pega-ConditionBuilder ruleset
Resolved in Pega Version 8.6
In Pega v8.2.5, the Pega-ConditionBuilder ruleset was added as part of the PegaMarketing application. When these enhancements were promoted to a platform ruleset beginning with Pega v8.4, the function names were modified with PZ/PX prefixes due to the corresponding validation standards in place for rules created in platform rulesets. Unfortunately, this introduced an upgrade impact. Due to the function name change, strategies failed when attempting to evaluate the functions configured in the filter component. Eg: @string.ContainsIgnoreCase function is part of the Pega-ConditionBuilder ruleset, which was not available. To resolve this, the following function aliases have been created in this release:ContainsIgnoreCase StartsWithIgnoreCase EndsWithIgnoreCase CompareDateTimeToSymbolicDate In addition, the pzGetFBData activity has been modified to ensure these function aliases are upgraded to the most current version available in the system and that assembly of the When rule or AccessWhen rules created in v8.2.5 perform as expected after Revalidate & Save or direct rule save actions performed after upgrade.
INC-209426 · Issue 706804
GetFunctionsForLibrary retrieves 10,000 rows
Resolved in Pega Version 8.7.2
Some functions were missing from the expression builder browser and search results when pyShowInternalLibrary was set to true for including internal functions in the results. To resolve this, the default value for "Maximum number of rows to retrieve" in pzGetFunctionsForLibrary has been increased to 10,000.
INC-209426 · Issue 706803
GetFunctionsForLibrary retrieves 10,000 rows
Resolved in Pega Version 8.8
Some functions were missing from the expression builder browser and search results when pyShowInternalLibrary was set to true for including internal functions in the results. To resolve this, the default value for "Maximum number of rows to retrieve" in pzGetFunctionsForLibrary has been increased to 10,000.
INC-164002 · Issue 639913
Decision table null input handling updated for backward compatibility
Resolved in Pega Version 8.5.4
After upgrade, any null values as inputs in the decision tables were skipped if "Allow Missing properties" was not checked. This behavior was different from previous versions. In order to improve backward compatibility, the new function pxEvaluateDecisionTable has been added which has an additional parameter to set AllowMissingProperties, and the older function logic has been modified to take the parameter value from the parameter page.
INC-164944 · Issue 636291
Logic updated to handle decision trees over 64k
Resolved in Pega Version 8.6
An exception was thrown when decision trees reached the 64K size limit. This has been resolved by modifying the logic in the DecisiontableMethodBody Rule-Utility-Function where the split size nPropRowLimit is based on the number of columns.
INC-140272 · Issue 595253
Report definition performance improvement
Resolved in Pega Version 8.6
Performance issues were seen with the pzOperatorsByWorkGroup report definition. This was traced to the report definition is adding an UPPER function for edit filter properties which caused it to take more time to run when combined with an ignore case check in the filters of the RD. This has been corrected.
INC-164944 · Issue 636292
Logic updated to handle decision trees over 64k
Resolved in Pega Version 8.5.4
Logic updated to handle decision trees over 64kAn exception was thrown when decision trees reached the 64K size limit. This has been resolved by modifying the logic in the DecisiontableMethodBody Rule-Utility-Function where the split size nPropRowLimit is based on the number of columns.