SR-C96571 · Issue 435174
Added check for visible SmartInfo so focus is maintained
Resolved in Pega Version 8.3
After setting up a harness that displayed page-level messages at the top and bottom with "info" icons in a grid that displayed SmartInfo, hovering on one of the "info" icons when a page-level message was displayed caused the page to scroll up to the page-level message at the top of the harness instead of displaying the SmartInfo popup. This has been resolved with the addition of a check for visible SmartInfo in pzpega_ui_doc_errors.js so the focus is properly set.
SR-D17249 · Issue 490109
Handling added to resolve Fusion chart tooltips issue in Google Chrome
Resolved in Pega Version 8.3
Tooltips for charts were not showing, and placing the mouse over the white area for the genaral tooltip in the charts made the white background blink. The error " Uncaught ReferenceError: FusionCharts is not defined at pyfusioncharts.theme.default_12208971721.js!!.js:1" was found in the Google Chrome console. Investigation showed that there was a recognition issue with Fusion charts when tooltips were enabled; this has been resolved by adding handling to check for an undefined value of the FusionCharts object within the declaration of the theme.
SR-D37943 · Issue 505735
Corrected Export to Excel after adding custom DateTime field
Resolved in Pega Version 8.2.4
An issue with exporting report definition results to Excel after adding a custom date field column through the edit report option of the report in report viewer was traced to the processing of the controls backing a cell in a report when exporting to Excel. For controls like "Date Only" DateTime (non-autogenerated) control, the code was not returning a string the way it should. To resolve this, NonAutoReportUIField has been updated to always treat all Non-auto Controls as strings.
SR-D36120 · Issue 506242
Escape added to Radio button field value to handle HTML tags
Resolved in Pega Version 8.2.4
A radio button with a field label to display a help icon and to open the help URL when the icon was clicked did not display as intended. Changing the control to text area produced the desired results. This was traced to the radio button's label being assigned to a field value which returned a string that at some points contained HTML tags, and has been resolved by escaping the pyLabelFor value before assigning it to the aria-label attribute of the radio button's div tag.
SR-D40617 · Issue 507565
Escape added to Radio button field value to handle HTML tags
Resolved in Pega Version 8.2.4
A radio button with a field label to display a help icon and to open the help URL when the icon was clicked did not display as intended. Changing the control to text area produced the desired results. This was traced to the radio button's label being assigned to a field value which returned a string that at some points contained HTML tags, and has been resolved by escaping the pyLabelFor value before assigning it to the aria-label attribute of the radio button's div tag.
SR-C96297 · Issue 433775
Enhancements added in support of AES/PDC integration
Resolved in Pega Version 8.3
The following enhancements have been added in support of AES/PDC integration: - QueueStatistics for Oracle and multi-tenant environments -Postgres statistics are reset after every push (this can be disabled by changing the DSS ResetTableStats) -Enabled Debug statements before all connect-rest/connect-soap calls -Handling for Listener Information issues -Elastic search updates -The connect timeout has been enhanced from 30 sec to 60 sec for all REST connectors. -Data pages can be used for picking the End point URL -Elastic Search Count details can be pushed to PDC
SR-D20439 · Issue 496404
Hotfix hashmap cleanup improved
Resolved in Pega Version 8.2.4
A DL installation failed with an out-of-memory error. It was observed that many CacheEntry(VersionedJdbcJarRwader.java) hashmaps were being created to store the details for each hotfix but that were then never cleared. This has been resolved by adding the finally block in CodeImportProcessImpl.java class to call the shutdown method for proper cleanup. In addition, the default command line utility (prpcUtils) has been updated to use JVM settings of Xmx 4GB and capture a heap dump if an out-of-memory error is encountered. The auto-generated prconfig.xml has also been updated to leverage its minimal startup setting which will avoid loading the conclusion cache into memory.
SR-C77730 · Issue 435797
Resolved case lock release improved
Resolved in Pega Version 8.3
Cases created through the create work object were unnecessarily holding onto locks for up to two hours. This was traced to a defer-write scenario for mobile devices which did not return the correct status needed for "no further assignments". In order to resolve this issue, a new parameter "returnNextActionInfo" of type boolean has been added to svcPerformFlowAction. This parameter will be always set as false when calling this activity from sync up so all locks will be closed and released.
SR-D3494 · Issue 439415
Enhanced REST acceleration wizard handling of existing properties during rule generation
Resolved in Pega Version 8.3
A resolution provided in an earlier release addressed the REST accelerator wizard failing when there was a property present in the @baseclass and that property was also present in the JSON input for data model generation. The error generated was "Cancelling rule generation. Definition required to conform to @baseclass.Name instance". This update further enhances that Rest wizard resolution to address case sensitivity issues in the naming, and adds additional support for scenarios where the property does not exist in the integration class or parent class by checking if the property exists in pyIntContextClass.
SR-D15495 · Issue 489736
Function in aggregate filter condition properly displayed
Resolved in Pega Version 8.3
After constructing a report definition with Filter conditions to apply after the aggregation filters with max as function, the function was not visible in the dropdown when the rule was opened. The Function was visible if the rule was checked out and remained visible if the checkout was discarded, but if the rule was opened and closed again the max function was not visible. This was traced to the Primary page not being considered properly while populating the data page D_pzGethavingFilterFunctions which loads the options for the filter dropdown. To resolve this, the activity pzHavingFilterFunctions has been modified to check for pzPrimaryHarnessPageName first before pzPrimaryPageName.