SR-D50819 · Issue 519237
Eligibility Builder integer sorting revised
Resolved in Pega Version 8.2.6
In 'Offer' on the Eligibility tab, the Builder was sorting integer properties by the value of the integer as a text string rather than the whole number. Example: 1, 10, 12, 13, 100, 2, 20, 29, 299, 3 instead of the expected 1, 2, 3, 10, 11, 12, 20, etc. This was traced to the system sorting the results using tools.sortPageList() in order to sort by localized (string) value, which is not appropriate for values of any type other than string. To resolve this, the system will skip the manual sort step for numeric columns since the values are appropriately sorted by the database.
SR-D53176 · Issue 541794
Error when adding function filter will persist
Resolved in Pega Version 8.2.6
When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.
SR-D55801 · Issue 524292
Corrected HTML error generated on export to PDF
Resolved in Pega Version 8.2.6
After exporting a report to PDF, the PDF could be viewed but repeated instances of the error "<th> missing ‘>’ for end of tag" were logged. This was traced to missing the closing '>' for th in the pzRRDataListHeaderRow HTML rule when "Enable column command menu" is unchecked in ReportViewer options, and has been corrected.
SR-D65256 · Issue 528006
DisplayCommandMenu holds value during runtime filter changes
Resolved in Pega Version 8.2.6
In report definition, under report viewer tab, the 'enable column command menu' option was disabled. When the report was launched, the menu was not displayed for each column as expected; after applying the filter changes, the column menu options were unexpectedly displayed. This was traced to previous work done on the implementation of the navigation menu for auto-generated grids. Because pyDisplayCommandMenu is exposed on the ruleform itself, disabling the command menu from the ruleform caused changes to the filter to reset and pyDisplayCommandMenu was set back to true regardless of what was configured on the ruleform. To correct this, updates have been made to ensure that pyDisplayCommandMenu is not overwritten when there are changes to a filter during runtime.
SR-D65327 · Issue 534570
Backspace keydown handler updated for all textinput modes
Resolved in Pega Version 8.2.6
Attempting to use the Backspace key to remove input from a number cell (either Integer or Decimal) did not work. When the action was performed by a Manager, the Backspace key works as expected. Investigation showed the logic in the keydown handler for the backspace key in pega_report_events.js was only ignoring the e.preventDefault() call when the textinput node type was text, not number or other input types. To correct this, the keydown handler has been updated so the backspace key in pega_report_events.js maintains the default backspace functionality for all textinput modes, not just those of type 'text'.
SR-D76943 · Issue 541371
SmartInfo icon functional for reports
Resolved in Pega Version 8.2.6
After enabling Smart Info for a list Report definition, the activity was not getting called and section was not getting displayed. Investigation traced this to encryption added in an earlier version which caused the SmartInfo API to receive a parameter in an unexpected format. Because this incompatibility would affect all APIs not compatible with the encryption, this encryption for the API has been reverted.
SR-D31734 · Issue 515656
Cross-site scripting protection added for parameter page properties
Resolved in Pega Version 8.2.6
An Cross-site scripting vulnerability was seen with the Edge browser when run on visibility on client check was enabled with dynamic layouts and some properties were accessed from parameter page. Because run on visibility on client check is not required in this scenario, is has been removed and the values will be accessed from the server instead.
SR-D37317 · Issue 512553
Run Ruleset Cleanup defaults to true
Resolved in Pega Version 8.2.6
After upgrade, the rule categories and rules were not showing correctly in the App view of the Dev Portal. Many warning messages were also logged related to the Decisioning DM Sample application. This was traced to the rules cleanup script not running properly. While there was a workaround of applying the ruleset cleanup scripts manually after removing the queries that reference the pr_engineclasses table, the cleanup will now be set to run by default (run.ruleset.cleanup=true). In addition, the logic to determine which RuleSets to include has been simplified and most of the pr4_rule_vw deletions have been combined.
SR-D38318 · Issue 519710
Data pages explicitly cleared after QP use
Resolved in Pega Version 8.2.6
The Util Node was showing as Offline in the Search Landing Page, and when Jobs were submitted for execution from other Nodes the message "Detected active run with unreachable nodes" was logged. The util node, configured as a backgroundprocessing node, was running QPs; the queue size for custom QPs is 500 messages /queue items per minute, but investigation showed the requestor level and thread level data pages corresponding to the QP activities were not being cleared after use. This led to high heap memory issues that made the node unreachable, and has been resolved by adding code to explicitly remove the data pages when processing has finished.
SR-D48396 · Issue 520423
Hazelcast upgraded to resolve node startup issue
Resolved in Pega Version 8.2.6
Post data upgrade, the ADM tier failed to start and the error "java.lang.IllegalStateException: Node failed to start!" appeared. This was traced to a dormant bug in Hazelcast 3.11 that caused starting nodes to fail when the Hazelcast master node was shutting down, which was exposed by recent Pega changes made to enable parallel restarts of nodes in Cloud environments. Hazelcast delivered a fix for the parallel restart problem and the hotfixed jar has been merged into the platform. In addition, previous logic for loading Admin Studio waited 30 seconds before timing out when fetching information for each node. This caused issues with large clusters and Admin Studio not loading. The logic has been updated in the Admin Studio UI to load the page despite delays/issues waiting for nodes to respond to the gathering of cluster data, and the algorithm to detect remote-call timeout has been updated and is applicable to batch operation.