SR-B36689 · Issue 292880
Performance improvements for CaptureInteraction without VBD
Resolved in Pega Version 7.3
CaptureInteraction was slow when not using a VBD server due to a call to the function GetVBDService that fired even when there was no intention to use VBD and it was not configured. This was an unintentional side effect of code that listens for VBD being ready in case it is in mid-initialization or cluster nodes are restarting. To improve performance, GetVBDService has been modified to avoid waiting for the VBD cluster if VBD is disabled using DSS prconfig/initservices/vbd/default = false.
SR-A102729 · Issue 272707
Mobile modal display timing corrected
Resolved in Pega Version 7.3
When the full screen for mobile device option was used while launching a local action, the template buttons (Submit and Cancel) appeared to be missing until the screen adjusted during a focus shift to an editable field. This was an issue with asynchronous display timing in the modal dialog template using dynamic layouts with client side visible whens, and has been fixed.
SR-D19081 · Issue 490370
Logic updated to handle Report Definition with a join
Resolved in Pega Version 8.3
When using a multi-select element on the UI with a report definition as a data source where the report used a join to another class where it was referenced by a prefix, setting that data source property as prefix.property resulted in the multi-select no longer showing any results when tested on the UI although the report definition returned results when run manually. This was traced to platform differences revealed by an upgrade, and the idGenerator function has been updated to handle a report definition with a join to resolve this.
SR-D39601 · Issue 509518
RRDisplaySection made available to assist Edge compatibility
Resolved in Pega Version 8.2.4
When the Pega Platform was being used with Microsoft Internet Explorer Compatibility Mode ON, it was not possible to use the select filter gadget due to a browser compatibility issue: enabling the filter condition for the report definition caused the SelectValues button to stick in loading mode when clicked. Changing the Microsoft Internet Explorer Document Mode for Harness pzRRDisplaySection to IE=Edge corrected the issue, but the rule was final. To resolve this, the pzRRDisplaySection has been made available to allow override for customers still using Microsoft Internet Explorer.
SR-D54984 · Issue 529208
Resolved ruleset save issue for Google Chrome/IE
Resolved in Pega Version 8.1.8
When using particular versions of Google Chrome or IE, the intermittent error "pyComponentInterfaceClass: <user> 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.
SR-C89619 · Issue 429573
Custom section filters retained during refresh
Resolved in Pega Version 8.3
Filtered values were not retained on refresh when filtered using a custom section. This has been resolved.
SR-C95253 · Issue 435786
Custom datetime controls correctly appended to Excel export
Resolved in Pega Version 8.3
The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.
SR-D10309 · Issue 482476
Custom datetime controls correctly appended to Excel export
Resolved in Pega Version 8.3
The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.
SR-B38578 · Issue 295917
Fixed null-pointer exception in external DB extract
Resolved in Pega Version 7.3
When using a class which maps to a table in an external database, running an extract caused a database permission error when trying to access the pr_log table in the PegaRULES database. This exception was caught and logged but then processing continued, resulting in a NullPointerException being thrown. To correct this, the sequence number generator has been modified to use the pr_log table instead of the class on which extract is defined.
SR-B38578 · Issue 272419
Fixed null-pointer exception in external DB extract
Resolved in Pega Version 7.3
When using a class which maps to a table in an external database, running an extract caused a database permission error when trying to access the pr_log table in the PegaRULES database. This exception was caught and logged but then processing continued, resulting in a NullPointerException being thrown. To correct this, the sequence number generator has been modified to use the pr_log table instead of the class on which extract is defined.