SR-B43024 · Issue 301959
Fixed focus issue for editing exported DT in Excel
Resolved in Pega Version 7.3
While editing a field in a column of a decision table exported to Excel, clicking "Insert OR After" caused the focus to be shifted to the end of the Decision table. This was traced to the sticky header applied for all the rules, and has been resolved by excluding the decision table and circumstance definition from the sticky header implementation in document.ready.
SR-B43160 · Issue 299701
Fixed up/down arrows for Firefox modal dialogs
Resolved in Pega Version 7.3
Up and Down arrows actions were not working in modal dialog text boxes when using Firefox. This was a defect in the framework, and has been addressed in modaldialog js.
SR-B43182 · Issue 301518
pzSUS Param properly URLEncoded
Resolved in Pega Version 7.3
The Tomcat 8+ server was rejecting DWA URLs due to characters such as {,} that it considered to be unsafe. These characters were introduced by pzSus key in the URL, and these values will now be encoded for the browser to resolve these issues.
SR-B43331 · Issue 302897
Help file updated for consequences of "Ignore Locale" setting
Resolved in Pega Version 7.3
Issues with date values were encountered in set ups where a localized Language Pack had been installed and developers used the "Operator Ignore locale preference" in Designer Studio in order to have Designer Studio in English. While the user portal was correctly translated and European format dates were accepted, an error stating "date is not a valid date value" would appear when a date time field was updated or a new ruleset was created. In order to ease the use of the setting, the help files have been updated to clarify that the "Ignore Locale" option on the Operator screen causes ALL locale settings to be ignored and the default en_US settings to be used. In addition to the display language, these settings include date, time and number formats.
SR-B43415 · Issue 299493
Upgrade does not exit when encountering corrupt ruleset name
Resolved in Pega Version 7.3
In order to avoid upgrade failures caused by an application rule existing without a version (corrupted data), handling has been added so that the upgrade will not fail if it encounters an application rule without either a name or version.
SR-B43493 · Issue 299133
DSS cleanup added for Pulse traffic
Resolved in Pega Version 7.3
An enhancement that reduced Pulse traffic across the Pega Platform Cluster had the side effect of leaving a dynamic system setting when a node was restarted. To correct this, VBD will automatically clean inactive dynamic system settings that were used for Pulse optimization. Inactive DSS for tracking nodes will be cleaned after 1 hour.
SR-B43621 · Issue 300812
Back/Previous years calculation fixed to use current year
Resolved in Pega Version 7.3
In the year dropdown for Date control, the number of back/previous years was calculated based on the selected year and not from the current year. The calculation logic has been fixed to resolve this.
SR-B43665 · Issue 301542
Accordion layout resizes correctly with IAC
Resolved in Pega Version 7.3
The "Accordion" layout was behaving incorrectly when the browser window was resized, preventing scrolling to the bottom of the page. This was an issue with layout groups configured with accordion not triggering a harness resize when clicked, and has been fixed.
SR-B43667 · Issue 300408
Data flow with RD secondary source honors filters
Resolved in Pega Version 7.3
When running a data flow that used a report definition as a secondary source, the report definition filters appeared to be ignored and the system pulled all records. The root cause of the issue was traced to the NativeSQL API, used to generate SQL out of Report Definition, removing some filter conditions unconditionally. For example SQL: select from
SR-B4391 · Issue 275319
GenerateGridHTML updated for JAWS version compatibility
Resolved in Pega Version 7.3
An update to the JAWS program caused it to no longer recognize some Pega grids as tables due to the use of role=presentation, and the table name was not associated with the layout header title leading to the tables not being labeled accordingly. To correct this, the GenerateGridHTML now has an added summary attribute in the ".gridTable".