SR-A6872 · Issue 216420
Filtering modified to allow searches with two-step filtering
Resolved in Pega Version 7.2
If a List View was being filtered by two columns, entering the first filter value into the "Search" text box (as opposed to selecting values from the pick list) in the filter popup caused the second filter operation to not return any results. This was an issue with the crossScriptingFilter, which has been modified to allow two-step filtering.
SR-A5814 · Issue 216307
Resolved blank list page navigation
Resolved in Pega Version 7.2
If there was a backslash (escape characters) in the double quoted report parameters passed from the section, no data was shown when navigating to the next page in a ListView report. This was caused by multiple encodings of the escape characters while moving back and forth between the pages. The filtering has been updated to correct this issue.
SR-A6387 · Issue 216159
Resolved errors while saving in summary view
Resolved in Pega Version 7.2
While saving an existing summary view, the error message "Output type: ** Your Field Definition does not match with Chart Definition. Verify it" was generated if only the third column was selected at the time of the save. In addition, selecting any checkbox other than the first in the chart's data tab during save of the summary throws an error. These issues have been fixed.
SR-A3914 · Issue 212709
Added null check to handle uninitialized object in prweb/PRServlet URL
Resolved in Pega Version 7.2
A NPE error was seen on the UI and in PegaRULES log when accessing PegaRULES URL when PRPC was deployed as an enterprise application and transaction type was "CMT" or "Container". This was found to be caused by the prthread object in EngineAPIclass not being initialized at the time the operation was called, and a null check has been added to handle such cases.
SR-A4720 · Issue 212436
Corrected focus for tabbing Ruleset inclusion data entry
Resolved in Pega Version 7.2
Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. This has been corrected.
SR-A4078 · Issue 211396
Eliminated duplicate results from Pega Usage Validation Utility (UVU)
Resolved in Pega Version 7.2
The Pega Usage Validation Utility (UVU) is a legacy tool for collecting data from older PRPC systems during system usage audits. Due to system changes, the results on newer installations included duplicate record counts caused by case differences between work table names. These duplicate records had the same work object ID but were coming from tables whose names were similar but with varying capitalization (Example_Table, example_Table, example_table). To avoid this issue, the ClassUsageDetail.equals() implementation has been updated to be case insensitive. There is also a newer tool available in the system to retrieve this data.
SR-A5645 · Issue 213208
Resolved FirstLogCreationTime error
Resolved in Pega Version 7.2
When the file PegaRULES-FirstLogCreationTime.log existed in the log directory, the following exception was generated: Exception caught while initializing context ... PegaRULES-FirstLogCreationTime.log exists, server cannot start". The file FirstLogCreationTime.log is a temporary file that gets created and used to hold the creation time stamp of the first log of the day (and help in avoiding the deletion of log files created in the previous day). If it becomes corrupted and is not readable, this error occurs. To correct this, code changes were made to make MaxBackupIndex applicable to all log files instead of only to log files of the day.
SR-A7611 · Issue 217142
Ampersand not rendered properly for DropDown
Resolved in Pega Version 7.2
In case of dropdowns with defer load, options having "&" were being double-encoded and displayed as '&'. The API has been updated to correctly handle the special character.
SR-A1440 · Issue 213844
Added catch for unspecified layout format
Resolved in Pega Version 7.2
Layouts saved without a format name were not rendering correctly; the container format was changed to 'other', which generated an exception due to the 'other' format not being available in the XML. To prevent this error, the layout format assignment is now wrapped in the JS with a try-catch.
SR-A3540 · Issue 210203
Added check for duplicate Date Control validation error
Resolved in Pega Version 7.2
In a screen flow, it is possible to move forward despite validation errors on the Date control. However, returning to the control caused the validation error message to be displayed twice. This was caused by both the server side and the client side generating the error. To correct this, logic has been added to check if the clipboard already has the messages defined in pClientErrors and avoid adding them to the clipboard if so.