SR-B42581 · Issue 299511
BIX enhancement to handle unaligned external mappings
Resolved in Pega Version 7.3
If a class with external mappings was configured and some of the properties did not match the db column name, a filter for one of those properties would not be applied to the extract query. In order to support business needs that contain the mis-match, an enhancement has been made to the BIX code to handle this non-alignment.
SR-B42586 · Issue 299297
Modified RD filtering rule to support custom validation
Resolved in Pega Version 7.3
Custom validation was not stopping a Report Definition from completing due to validation errors not being applied to the correct page when submitting the form. In order to support this customization, pzValidateCustomFilterSection has been modified to put messages on the step page rather than primary page.
SR-B42586 · Issue 300843
Modified RD filtering rule to support custom validation
Resolved in Pega Version 7.3
Custom validation was not stopping a Report Definition from completing due to validation errors not being applied to the correct page when submitting the form. In order to support this customization, pzValidateCustomFilterSection has been modified to put messages on the step page rather than primary page.
SR-B42911 · Issue 301591
Tomcat config documentation clarification
Resolved in Pega Version 7.3
The documentation for using Tomcat has been updated for clarity. Step 2b of 'Configuring Tomcat by editing the context.xml file' indicates that configuration of the Admin datasource is optional (which it is), but steps 3 and 4, which use this datasource, were not labeled as conditional on 2b. As a result, those opting not to use the admin datasource believed those settings needed to be added. In the new text for steps 3 and 4, the clarification "For dual-user configurations only, insert..." has been added.
SR-B42964 · Issue 302624
History table updates with data table record deletion
Resolved in Pega Version 7.3
The Deletion of the record from a data table was not adding an entry into History table. This behavior has been changed with a "History-Add" step in the pzDeleteRecord activity.
SR-B42964 · Issue 302338
History table updates with data table record deletion
Resolved in Pega Version 7.3
The Deletion of the record from a data table was not adding an entry into History table. This behavior has been changed with a "History-Add" step in the pzDeleteRecord activity.
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.