INC-168885 · Issue 663668
Corrected restoring lockable data class
Resolved in Pega Version 8.7
After opening an instance of a lockable data class and deleting it and then restoring it, the system reported an error that a lock can't be held on the instance. This only happened for lockable data instances that were deleted and restored immediately, and as a work around the item could be restored successfully from from the History- instance. To resolve this, the pzRMActionRecoverDeleted activity has been updated to copy to a temporary page and take action instead of acting on the primary page.
INC-168914 · Issue 659659
Updates added against Cross-site Scripting
Resolved in Pega Version 8.7
Cross-site Scripting (XSS) protections have been updated for the UI.
INC-169063 · Issue 649986
Referencing tool sorts rules by ruleset and version
Resolved in Pega Version 8.7
After opening the View Reference tool with all rule set versions, the sort resulted in rules in multiple versions saved out of order. This has been resolved by adding two obj-sorts to ensure that the sort order appears as expected.
INC-171257 · Issue 651734
Expanded results for Proposition Filter Relevant Record Properties
Resolved in Pega Version 8.7
Previously, a maximum of 500 records were returned from pr_data_tag_relevantrecord when using Edit Parameters for the report definition proposition filter rule. In order to accommodate more complex needs, an update has been made to use the D_pxGetClassDataModel data page to fetch all the records and make them available in the dropdown.
INC-174200 · Issue 650293
Corrected typo in App Menu
Resolved in Pega Version 8.7
In the Data-Portal.pzAppMenu rule, the entry for the disabled version of New Application was misspelled. This has been corrected.
INC-174435 · Issue 659478
Survey Complex Question Definition properly displayed
Resolved in Pega Version 8.7
Selecting any Complex Question to look at the definition displayed a blank screen. This was traced to an issue with the ruleformtabs properties for the layout group used by complex questions, and has been resolved by changing the Layout Group display type from "Default" to "Tab".
INC-174468 · Issue 650946
Delegated rules search considers localized text
Resolved in Pega Version 8.7
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-175533 · Issue 678909
Improved Page compare for page groups
Resolved in Pega Version 8.7
Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.
INC-176542 · Issue 668478
Removed unused function to improve Class rule save performance
Resolved in Pega Version 8.7
Clicking save on the Policy Class rule was not working correctly or was taking an excessive amount of time to respond. Adding property mapping in the External Mapping tab of the Class rule exhibited the same behavior. Investigation showed there was an infinite loop being invoked in the class ruleform, which was traced to the disableKeyEntries() function. As this function is no longer used, this has been resolved by updating the RF_RuleObjClassScript.js to remove disableKeyEntries and any function calls to it.
INC-178070 · Issue 658678
Browser invocation allowed for UnlockOperator
Resolved in Pega Version 8.7
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.