INC-164944 · Issue 636289
Logic updated to handle decision trees over 64k
Resolved in Pega Version 8.4.5
An exception was thrown when decision trees reached the 64K size limit. This has been resolved by modifying the logic in the DecisiontableMethodBody RUF where the split size nPropRowLimit is based on the number of columns.
INC-168094 · Issue 642625
Security updated for help URL infrastructure
Resolved in Pega Version 8.4.5
Cross site scripting protections have been added to the help URL infrastructure.
INC-168914 · Issue 659658
Updates added against Cross-site Scripting
Resolved in Pega Version 8.4.5
Cross-site Scripting (XSS) protections have been updated for the UI.
INC-169203 · Issue 646099
Robotics Desktop Automation correctly runs on subsequent tabs
Resolved in Pega Version 8.4.5
When using Customer Service (CRM) to call Robotics Desktop Automation (RDA) from a data page, closing the first interaction tab after the RDA automation was completed resulted in the automation not being triggered for the second tab. If the first tab was not closed, the automation on the second worked as expected. Investigation showed the attachOnUnload was unregistering the client actions for all the open tabs and the attachOnLoad was not being called on reload. This has been resolved by updating attachOnLoad so it is now called with InvokeOnReload as 'true' to register client action for the tab in focus.
INC-174468 · Issue 650945
Delegated rules search considers localized text
Resolved in Pega Version 8.4.5
The search / filter box used to look for particular delegated rules on the configuration tab did not consider localization via field values, where the on screen name and description of the delegated rule was localized. This resulted in the search text being compared against the original text (.pyAdviceText and .pyDescription) used for the name and description at the time the rule was delegated, but not with the localized text that actually appeared on the screen. This has been resolved by updating the pzPopulateDelegations activity to filter by localized values of pyAdviceText and pyDescription.
INC-178070 · Issue 658424
Browser invocation allowed for UnlockOperator
Resolved in Pega Version 8.4.5
Attempting to unlock an operator who was locked out due to security policies was failing. This was an unintended side effect of security work performed earlier, and has been resolved by reenabling 'Allow invocation from browser ' for pzUnlockOperator. This activity requires an authentication check with privilege protection.
SR-D44942 · Issue 518354
Guided tour popups handling added for right-to-left language locales
Resolved in Pega Version 8.2.6
Guided Tour Popups were still appearing in the default EN location after switching to the ar_AR locale. This was traced to a missed use case for locales using a right-to-left mode such as Arabic or Hebrew, and has been resolved by updating the guided tour engine openPopOver function to account for the HTML tag dir attribute for value of "rtl". This will anchor the pop over to rightBottom / and display the arrow on the rightTop instead of leftBottom / leftTop.
SR-D52138 · Issue 537505
Property setting corrected for On Join and Exclusion shapes in Expression Builder
Resolved in Pega Version 8.2.6
The properties for the defined page did not appear when using the type-ahead feature to select properties for the On Data Join and Exclusion shapes in Expression Builder. This was an issue related to the property being referenced for setting the context in the expression builder, and has been corrected.
SR-D54963 · Issue 524114
Updated Decision Table validation for multiple OR conditions
Resolved in Pega Version 8.2.6
When the Decision Table had multiple OR conditions, the table was verified as consistent even when two rows had the same value. Analysis showed that when Show Conflicts encountered multiple 'or' conditions in a row that matched the same conditions in other rows, it considered them to be different rows. This has been corrected.
SR-D54984 · Issue 529209
Resolved ruleset save issue for Google Chrome/IE
Resolved in Pega Version 8.2.6
When using particular versions of Google Chrome or IE, the intermittent error "pyComponentInterfaceClass: does not exist or is not a valid entry for this ruleset and its prerequisites" appeared when attempting to validate an application, and the ruleset could not be saved. This was traced to changes made in the browser around password handling, and has been resolved by explicitly clearing out the pyComponentInterfaceClass if that value is not in use.