INC-153697 · Issue 625984
Dragon successfully navigates to user profile icon
Resolved in Pega Version 8.5.3
Attempting to navigate to the user profile icon when using Dragon software was not working. This is an issue with how Dragon interacts with the "< I >" element operator icon, and has been resolved by replacing "< i >" with a button and appropriate aria label.
INC-155401 · Issue 630448
Circumstance Definition rules save correctly
Resolved in Pega Version 8.5.3
After upgrade, attempting to save any circumstance definition that used multiple "or" conditions consistently failed during conflict detection. This was an inadvertent side effect of work done to resolve an out of memory error and has been resolved by modifying the Rule-Declare-!testConsistency java step:"int numRows = numOrs;" to"int numRows = numSubRows;".
INC-159238 · Issue 624304
Handling added for identical property and page names in test case recording
Resolved in Pega Version 8.5.3
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 629646
Upgrade compatibility enhanced for Pega-ConditionBuilder ruleset
Resolved in Pega Version 8.5.3
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
INC-160446 · Issue 627381
Updated Time Zone dropdown control
Resolved in Pega Version 8.5.3
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 time zones. 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 data page.
INC-162881 · Issue 636992
Decision Table check-in warnings supported for large tables
Resolved in Pega Version 8.6.1
After adding an empty row in the middle of Decision Table rows and checking in, the Decision table rule's CheckIn form shows a functionality warning about a conflict in decision table ("This rule contains 1 logic conflict(s). Click the 'Show Conflicts' button for more details."). However, this behavior did not occur as expected if the decision table had more than 500 cells in it, and has now been resolved.
INC-164002 · Issue 639912
Decision table null input handling updated for backward compatibility
Resolved in Pega Version 8.6.1
After update, 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-164171 · Issue 644705
Support added for connect-SOAP run in parallel mode
Resolved in Pega Version 8.6.1
When connect-SOAP was configured to use the “run in parallel” mode, application settings derived through a datapage had incorrect values. While running the connect-SOAP through an activity, all the values were derived incorrectly. This has been resolved by adding a synchronization enhancement to support parallel run connect.SOAP.
INC-164439 · Issue 657997
Setting added to customize using blank Map values
Resolved in Pega Version 8.6.1
After update to from Pega 6 to Pega 8 some of the Map Value rules were not working. This was due to the handling for blank default values which was changed in Pega 7. In order to support backwards compatibility, a new 'when' rule has been added which allows customizing whether or not blank values are allowed for the Map value default columns. pyAllowBlankValues will default to "false".
INC-165256 · Issue 657038
Improvements for Offer Eligibility rules loading time
Resolved in Pega Version 8.6.1
After opening the Proposition filter/Action rule and clicking on Add Criteria, the pxAnyPicker drop down load was taking an excessive amount of time. Performance improvements have been made by adding a precondition at step 2 to avoid data page refresh for specific scenarios when it is not required.