INC-159238 · Issue 624305
Handling added for identical property and page names in test case recording
Resolved in Pega Version 8.6
When trying to record a test case, the error "WrongModeException: The property PostProsSnapOfWorkpage.Name was of mode String while com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getPageValue() was expecting Page mode" was generated. This was an edge case caused by property and page names being the same on the "PostProsSanpOfWorkPage" page, and has been resolved by accessing the page with the full path so it has the proper prefix.
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-160446 · Issue 627380
Updated TimeZone dropdown control
Resolved in Pega Version 8.6
The RF_Timezonelist control was deprecated in Pega v8.4 and withdrawn in Pega v8.5 and a replacement datapage was provided to give the same list of timezones. Unfortunately, some references were not corrected to point to the replacement, causing an issue with custom functions that were attempting to set the time zone on an OperatorID calendar instance in order to calculate goal and deadline properties before setting the SLA. The work has been reviewed and updated to ensure all referencing rules are now correctly replacing the RF_Timezonelist with a dropdown sourcing the datapage.
INC-160603 · Issue 629944
Removed development test log message
Resolved in Pega Version 8.6
The message "came to my actiovity branchhhhhhhhhhhhhhhhhhhhhhhhhhhhh" appeared multiple times in the log, and was traced to clicking on the refresh button of the Application Quality Dashboard page. This was an oversight log message inadvertently left in place after development work, and has been removed.
INC-163970 · Issue 636136
Expression Builder updated for special character handling
Resolved in Pega Version 8.6
If a modulo operator (%) was used in expression builder, the expression showed the correct value when it was submitted (closed) but on reopen the expression was changed and not calculated correctly. If the expression was not reopened then it calculated the value properly. This issue was traced to a server call to pzEvaluatePegaExpression which treated certain values as containing special characters, and has been resolved by updating the handling for this scenario.
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-133214 · Issue 590380
Deployment Manager rollback works for directed inheritance
Resolved in Pega Version 8.6
Rollback was not working correctly in Deployment Manager for history classes using directed inheritance. This was traced to a redundant check in AbstractHistoryPageKeeper that enforced the history pages pattern inherited from one of the base history classes, and this has now been removed.
INC-140040 · Issue 597666
Improved handling to ensure circumstanced rules skim is complete
Resolved in Pega Version 8.6
After performing a major rule skim, it was noticed that some of the circumstanced rules were not carried over to the higher version. The data was restored and a second skim was attempted. Once again, not all of the circumstanced rules were carried over; however, the results were different than in skim 1. This issue was traced to the circumstanced rule and base rule having the same pxCreateDateTime because they were processed with in a millisecond span. To resolve this, a 1ms explicit sleep has been added before processing each record.
INC-140279 · Issue 597757
JMX logging added to upgrade diagnostics
Resolved in Pega Version 8.6
In order to improve diagnostic information, infoForced loggers have been added for debugging upgrade issues related to JMX calls to enable and disable rules creation.
INC-142236 · Issue 595979
Apache Struts updated
Resolved in Pega Version 8.6
The Apache struts2-core.jar and its dependencies have been updated to version 2.5.25.