SR-D29416 · Issue 500133
Email template content editors visible when using Smart Investigate
Resolved in Pega Version 8.2.3
When specialized email correspondence templates were used with the Smart Investigate Framework, the correspondence rules did not have all the default values used in visibility conditions. This caused the 'when' rules pzShowSourceOnlyEmailEditor and pzShowBasicEmailEditor to evaluate to false and not display the source stream. To resolve this, UpgradeOnOpen has been added for correspondence rules to set the value for the visibility of rich text editor for source code viewer in order to support the use of custom templates with Smart Investigate Framework.
SR-D18879 · Issue 500641
Logic update made to PrepareColors to resolve calculation ambiguity
Resolved in Pega Version 8.2.3
When a Report Definition was summarized, the executed report showed a graph for multiple categories but generated the error "No data to display" if given a single category. This was traced to an ambiguity in the Java syntax of the RUF pzPrepareColors that led to a NegativeArraySizeException on a customer's environment. To resolve this, parentheses have been placed around a ternary operator to ensure the correct order of operations.
SR-D32222 · Issue 500899
Auto-generated controls with images supported in export to Excel
Resolved in Pega Version 8.2.3
When attempting to display a column as an image, changing the column format to "pxCheckbox" showed an image while running the report if the value was true, but blank values were displayed when the report was exported to Excel. Investigation showed that the value was being returned as null when a boolean value was set on a column and the option for the auto control was set to show as an image due to the formatted value being returned as an HTML element instead of a boolean value. To correct this, AutoGenReportUIField has been modified so that auto-generated controls that are shown as images are converted to text upon export to Excel.
SR-D26641 · Issue 501020
Truncate now considers empty Cassandra cluster as proper DDS state
Resolved in Pega Version 8.2.3
After setting up two external Cassandra DDS nodes with data sets, decommissioning one node and running truncate resulted in the exception "Truncate cannot be performed due to an inconsistency in the Cassandra cluster status". This was traced to the empty cluster being considered an improper state of DDS that then failed a consistency check, and this has been resolved by modifying the consistency check behavior to consider an empty cluster as a proper state of DDS.
SR-D24682 · Issue 501079
Added check for undefined targetTD in repeating tab layout
Resolved in Pega Version 8.2.3
Given a repeating tab layout and a validation on the flow action which used edit validate, clicking on the next button set an error on the page. Putting in the correct data and clicking the next/submit button a second time resulted in a console error indicating the targetTD was undefined for the markSectionTabErrors function in pzpega_ui_doc_tabsupport. This has been resolved by adding a check for the undefined targetTD.
SR-D33421 · Issue 501114
DX API - Field values for placeholder text localized
Resolved in Pega Version 8.2.3
While using DX API, it was observed that if a field value was used for displaying placeholder text, the field value rule was not resolved. Instead, the name of the field value rule was passed in JSON as text and not the actual value. This has been corrected by adding pyNoSelectionText to specifically localize the placeholder text for dropdown.
SR-D26244 · Issue 501192
Label control XSS protection added
Resolved in Pega Version 8.2.3
XSS protection has been added to label control.
SR-D31336 · Issue 501286
Dropdowncontrol shows correct value in read-only mode
Resolved in Pega Version 8.2.3
The dropdown control was not showing the correct value in read-only mode when the standard value of one option was the same as the prompt value of another. Investigation showed that in read-only mode, the loop to fetch the selected value from the datapage results was not stopping when it found an exact match. This has been resolved with the addition of a break statement.
SR-D22075 · Issue 501344
Wild card character escape added for filtering data records
Resolved in Pega Version 8.2.3
It was not possible to export data type records which were filtered with either _ or % in the value. This was due to the characters being wild card characters in the SQL-like operator, and has been resolved by modifying the NativeSQLAPIResolver to add escapecharacter to the runtime value of the filter.
SR-D27528 · Issue 501370
Return from drilldown in frameless portal corrected
Resolved in Pega Version 8.2.3
Drill up after drilling down on a dashboard chart in a frameless portal (such as Case Worker or Case Default) was throwing an exception. This was caused by the top-level page generated during drilldown not having pyRetainPage set to true, causing it to be removed from the clipboard by doUIAction. This has been resolved by updating runReport to set pyRetainPage if it needs to create the top-level page.