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.
SR-A6010 · Issue 215099
Added handling for special characters in RUF labels API
Resolved in Pega Version 7.2
A change in the handling of special characters such as quotation marks was causing compiler errors after upgrade. This was traced to the StringUtils.escapeIntoJavaString api for label generation in generateCellContent RUF and has been corrected.
SR-A6636 · Issue 215085
Added missing hover text for closing work object
Resolved in Pega Version 7.2
Hovering the mouse over the "X" (Close) icon in a work object was displaying the same message given when hovering over the tab. This was due to a missing "Title" attribute in the dynamic container, and has been fixed.
SR-A6636 · Issue 215085
Added missing hover text for closing work object
Resolved in Pega Version 7.2
Hovering the mouse over the "X" (Close) icon in a work object was displaying the same message given when hovering over the tab. This was due to a missing "Title" attribute in the dynamic container, and has been fixed.
SR-A3384 · Issue 212375
Added negation(!) handling for 'when' functions in icon control
Resolved in Pega Version 7.2
After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.
SR-A3384 · Issue 211149
Added negation(!) handling for 'when' functions in icon control
Resolved in Pega Version 7.2
After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.