SR-D15261 · Issue 487509
Added ability to edit or SaveAs OOTB 'Case Volume' report
Resolved in Pega Version 8.2.3
It was not possible to perform Edit or Save As to a Private category for the Pega out-of-the-box report 'Case Volume', which is under the Public category 'Case Metrics'. This was traced to certain OOTB report definitions being saved with a pz prefix which does not support the "Save As" functionality, and has been resolved by adding a Property-Set step above "Call pxCreateRecord" to set .pyRuleAvailable to "Yes".
SR-D15262 · Issue 486887
GetNextWork properly switches applications for 'most urgent'
Resolved in Pega Version 8.2.3
Post upgrade, the "Get most urgent" button was unable to open a service request from another application to which the operator had access. In this case, the Operator had access to the Canada and USA applications by default, but when a service request from the Canada application context was available in the list, the Get most urgent functionality failed to switch the application context from USA to Canada in order to open the work item. Investigation showed that the GetNextWork activity was being overridden in the Pega-DecisionManager ruleset in rule resolution and that the the Pega-ProcessEngine and Pega-DecisionManager had different versions of the activity. This has been resolved by upgrading GetNextWork in the Pega-DecisionManager ruleset.
SR-D15275 · Issue 490023
Report title displayed properly when prompting for filter changes
Resolved in Pega Version 8.2.3
Launching a report from the report browser showed a blank for "Report tab title" if the option "Prompt for filter changes before displaying report" was checked. This has been corrected by adding pzRDWinTitle to the harness Code-Pega-List.pzRRDisplaySection so it will display the name of the report when prompting for filter changes.
SR-D15425 · Issue 487885
Removed extra space from feld value in Audit History
Resolved in Pega Version 8.2.3
A space was seen for a Field value that was referenced in the instructions Audit History. This was traced to the control adding an extra space if any gaps were present in the code, and has been resolved.
SR-D15428 · Issue 491566
Null check added to resolve non-impacting InvalidParameter exception
Resolved in Pega Version 8.2.3
Creating a child case from the SLA goal activity using the 'AddCovered' activity generated the message "Exception in queue item: cannot be null or blank". The error "com.pega.pegarules.pub.clipboard.InvalidParameterException: cannot be null or blank" was also seen. However, no functionality impact was observed. This has been resolved by adding a null check to the getPortalName method, and modifying the HarnessUIBuilder.java file to add safe checks for whether 'portalName' is empty or not.
SR-D15469 · Issue 487522
Export to Excel formats the DateTime filter for localized values
Resolved in Pega Version 8.2.3
When exporting to Excel, filter criteria were given in GMT rather than the localized timezone. This was caused by the implementation of localizeDateTimeString method not formatting the output string for the locale/timezone during export to Excel, and has been corrected to display the localized filter values when the filter values include DateTimes.
SR-D19491 · Issue 489901
Export to Excel formats the DateTime filter for localized values
Resolved in Pega Version 8.2.3
When exporting to Excel, filter criteria were given in GMT rather than the localized timezone. This was caused by the implementation of localizeDateTimeString method not formatting the output string for the locale/timezone during export to Excel, and has been corrected to display the localized filter values when the filter values include DateTimes.
SR-D15520 · Issue 497155
Exported formatting corrected to display security scan line found detail
Resolved in Pega Version 8.2.3
Running a Rule-Security-Analyzer scan using a pyUnsafeURL regular expression and RSA provided items found, but the exported results did not contain line found detail. Investigation showed this was caused by the results being converted to an HTML table when the result itself contained HTML tags, resulting in broken HTML generation. To resolve this, the results will be sanitized for display as HTML.
SR-D1575 · Issue 483122
Added check for null work page in Pulse task
Resolved in Pega Version 8.2.3
After upgrade, the message "Error in Pega Log file:Unkown Error: Error during while executing pulse task: SingleCaseMetricsManagerFlush java.lang.NullPointerException: null" appeared while executing Pulse task. This was traced to a null workObjectPage, and has been resolved by adding a check for a successfully created work page.
SR-D15822 · Issue 485164
PageList under PageGroup Repeating Layout corrected
Resolved in Pega Version 8.2.3
An issue with the PageList under PageGroup Repeating Layout not working has been resolved by modifying the system so the initial "." will not be removed when using a page from a property. In addition, the newRow functionality has been updated to support the use of an embedded pagelist in a page list.