INC-175707 · Issue 655349
Multi-level strategy gives correct rules during Batch run
Resolved in Pega Version 8.4.5
When using a nested page structure with multi-level strategies that loop through each page and process the customer, a customer with two linked customers A and B had the results of A overridden by B during Batch Processing while single case canvas testing showed the correct results. This was caused by the DSM clipboard page method of carrying the parent page info not supporting the re-use of pages, and has been resolved by adding an enhancement that will sanitize the strategy stage processor to ensure the correct page reference is used.
INC-146098 · Issue 633721
Keyboard shortcuts work in Decision Trees
Resolved in Pega Version 8.4.5
Keyboard short cuts in Decision Trees used to copy/paste by holding ctrl button in Decision Trees were not working. This was an unintended side effect related to changing non-auto grid to an auto-generated hierarchical table to make the Decision tree rule form multi-browser compatible, and has been resolved by adding cut/copy/paste/insert-after/insert-before functionality to the decision tree context menu.
INC-151662 · Issue 626575
Handling added for application which includes production ruleset
Resolved in Pega Version 8.4.5
When creating the Email channel or Webchat channel, the Text Analyzer and its respective class (Data-Decision-Request-MCP-WebChat-xxxxx) was being saved in the ruleset of the built-on application while there were rulesets open in the top application. This was a missed use case, and has been resolved byupdating the logic to account for the scenario where an application includes a production ruleset.
INC-153697 · Issue 625982
Dragon successfully navigates to user profile icon
Resolved in Pega Version 8.4.5
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 630447
Circumstance Definition rules save correctly
Resolved in Pega Version 8.4.5
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 624302
Handling added for identical property and page names in test case recording
Resolved in Pega Version 8.4.5
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-161609 · Issue 628996
Unneeded configuration window close icon removed
Resolved in Pega Version 8.4.5
JAWS was not reading the configuration window close icon. This was an outdated control that should have previously been removed from this section, and has now been withdrawn.
INC-162881 · Issue 636991
Decision Table check-in warnings supported for large tables
Resolved in Pega Version 8.4.5
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-163970 · Issue 636135
Expression Builder updated for special character handling
Resolved in Pega Version 8.4.5
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-164439 · Issue 657996
Setting added to customize using blank Map values
Resolved in Pega Version 8.4.5
After upgrade 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".