SR-D21527 · Issue 491738
Hidden filters will not be shown on the resulting report
Resolved in Pega Version 8.1.6
After setting up a Report Definition to be visible in report browser with all filters hidden, editing and saving the report resulted in the filter values being visible on the report. This has been resolved by modifying pzResolveCopyFilters activity so that If the filter view option is "Read only, allow no changes" and "Filter not visible in Viewer", it will skip copying the filter values on to the report definition page.
SR-D32441 · Issue 502575
Multiple-nodes rebuild LibraryMetadata to ensure all RUFs are present on change
Resolved in Pega Version 8.1.6
When performing a complete Application import into a clean installation, references to certain Rule-Utility-Functions went unresolved during the initial assembly. Investigation showed that after introducing a new Rule-Utility-Library or Rule-Utility-Function on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that RUL. Therefore, assemblies on those other nodes could throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation, to ensure that each node completely rebuilds the LibraryMetadata for that RUL so it contains all the RUFs.
SR-D6721 · Issue 488973
Updated report widget drilldown logic for better non-ASCII character support
Resolved in Pega Version 8.1.6
When a report in the report widget had a drilldown chart with a parameter containing certain non-ASCII characters, no entries for the drilldown filter were shown even when there was data that matched that filter. This was traced to the drilldown JavaScript for dashboard report widgets encoding the drilldown parameter twice, causing characters that were Unicode but not ASCII to be corrupted. This has been resolved by updating the logic for pzpega_chart_legacydrilldown.js and pzpega_control_actions_reportdefinition.js to ensure the parameter is not encoded twice.
SR-D8390 · Issue 488003
Handling added for runtime exception on upgrade due to inaccessible external schema mapping
Resolved in Pega Version 8.1.6
If a system used external schema mapping, attempts to upgrade were failing with the error "Caused by: com.pega.pegarules.pub.database.ConfigurationException: Unable to obtain data source "java:comp/env/jdbc/PegaRULES", as it is undefined". This was traced to configuring external DADNs which were not accessible from the server where the upgrade was being run: an upgrade will fail if it cannot connect to an external datasource even if no changes need to be made to that datasource. However, because a PRRuntimeException was unexpectedly being thrown instead of a Database Exception, the exception was not properly caught and handled. This has been corrected.
SR-D9142 · Issue 482314
Support added for custom JVC arguments for Cassandra
Resolved in Pega Version 8.1.6
An enhancement has been added to support specifying custom JVM arguments for Cassandra. This allows uses such as enabling GC logging for cloud deployments, or to increase the native transport queue size for read-heavy deployments.
SR-D17825 · Issue 494701
PreSaveAs updated to set the correct ruleset value when saved into a different ruleset
Resolved in Pega Version 8.2.3
When using a BIX Extract rule already configured with properties and filter criteria, attempting to update the filter criteria system resulted in an "invalid property error" and inability to save the updated rule. This was traced to the extract rule being created from another extract rule with 'save as', resulting in the new extract existing in a different ruleset. Because the pxBixReportPage.pyRuleset had the value of the original ruleset instead of rule set in which it had been saved, the system was attempting to find the filter properties in the original ruleset. To resolve this, the Presaveas activity in rule-admin-extract has been modified to check and set the correct value when both the rulesets are not equal.
SR-D18038 · Issue 489532
Corrected grid column header misalignment
Resolved in Pega Version 8.2.3
After upgrade, a grid's first column heading was misaligned when using the IE browser. This was traced to Quirks mode related CSS not being removed after support for Quirks mode ended, and has been corrected.
SR-C94644 · Issue 485244
Date Filter corrected for Optimized table layout
Resolved in Pega Version 8.2.3
The Date Filter was showing incorrect results when 'next month/current month' range filter was applied on the 31st of the month and the Allow Optimize code check box was enabled in the table layout properties. This was traced to the pySymbolicStartDate and pySymbolicEndDate properties values not being properly populated with time, and has been corrected.
SR-D11312 · Issue 484683
CKEditor table-related plugins updated
Resolved in Pega Version 8.2.3
In order to successfully put a copy of previous correspondence below the auto email template, gaps had to be explicitly left below the auto email template before pasting the previous email correspondence. Otherwise the auto template disappeared and left only the previous email correspondence on the auto template. This was traced to issues with the CKEditor plugins, and has been resolved by updating to the latest table plugins from CKEditor (table,tabletools,showborders,tableresize,tableselection).
SR-D16624 · Issue 490927
Table layout filter popover position corrected for Pega mashup
Resolved in Pega Version 8.2.3
When using an exposed harness with table layout using Pega web mash up, the mash up worked but the apply and cancel buttons were not visible when any column was clicked to filter the result. This was traced to the filter popup having a hardcoded position offset set in its div element, and has been resolved by delegating the responsibility of the filter popover height calculation to the popover.