SR-D26505 · Issue 484426
Check added to isConnectorProblemFlow for empty newAssignPage
Resolved in Pega Version 8.3
When the isConnectorProblemFlow 'when' rule had a "newAssignPage.pyErrorStep = .pxFlow(newAssignPage.pyFlowInError).pyLastFlowStep" condition and was triggered on click of an actions button in the review harness, an error appeared. This was traced to newAssignPage being an empty page group property reference, and the issue has been resolved by adding a check to isConnectorProblemFlow for the existence of newAssignPage before referring to a property in it.
SR-D15520 · Issue 484531
Exported formatting corrected to display security scan line found detail
Resolved in Pega Version 8.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-D11312 · Issue 484681
CKEditor table-related plugins updated
Resolved in Pega Version 8.3
In order to successfully put a copy of previous correspondence below the auto email template, gaps had to be explicitly left below the auto email template before pasting the previous email correspondence. Otherwise the auto template disappeared and left only the previous email correspondence on the auto template. This was traced to issues with the CKEditor plugins, and has been resolved by updating to the latest table plugins from CKEditor (table,tabletools,showborders,tableresize,tableselection).
SR-D9482 · Issue 484738
Small delay added to autocomplete control
Resolved in Pega Version 8.3
When using an autocomplete control with minimum character search set to 4, every keystroke after 4 characters triggered a REST request to populate the control. This had a negative impact on performance. In order to smooth the request process, the timing logic has been updated to allow for a very small delay on the immediate event handler.
SR-D11296 · Issue 484856
Microsoft Internet Explorer Flex layouts updated to mode 7.0
Resolved in Pega Version 8.3
Given a grid with 8 columns in the Agents Landing page, the columns on each end were distorted when viewing the grid in IE. This was an issue with the class flex-grid-table-wrapper not correctly handling scenarios where grid cells containing section includes were not visible, and has been corrected by updating pzagentscheckbox and pzagentsstatus to layout mode 7.0 so zoom is supported.
SR-D15391 · Issue 484920
Add row works as expected when using Embedded Elsewhere with a modal grid
Resolved in Pega Version 8.3
When using Embedded Elsewhere, add row was not working on the first attempt for a grid launched inside a modal dialog. Changing the focus then resulted in the added row appearing. This has been resolved by updating the timing for the performInsertAction in the ui_grid JS.
SR-D15822 · Issue 485162
PageList under PageGroup Repeating Layout corrected
Resolved in Pega Version 8.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.
SR-D13388 · Issue 485167
Handling added for minor case creation errors
Resolved in Pega Version 8.3
When creating a case, if any step status failed due to a non-critical reason which did not impact case creation (for example, a mandatory parameter was missing from the data page), that failure state was propagated to SaveNew and ultimately to the case creation API. As a result of this failure report, no case ID information would be reported back to the requestor even though the case was created, and the API responded with status 500 - internal service error. This has been resolved by removing the StepStatusFail check from pzCreateCaseInternal so that non-breaking errors will not result in a 500 error, and a check has been added for page messages in svcAddWorkObject and svcPerformFlowAction so that validation messages are returned.
SR-D6721 · Issue 485208
Updated report widget drilldown logic for better non-ASCII character support
Resolved in Pega Version 8.3
When a report in the report widget had a drilldown chart with a parameter containing certain non-ASCII characters, no entries for the drilldown filter were shown even when there was data that matched that filter. This was traced to the drilldown JavaScript for dashboard report widgets encoding the drilldown parameter twice, causing characters that were Unicode but not ASCII to be corrupted. This has been resolved by updating the logic for pzpega_chart_legacydrilldown.js and pzpega_control_actions_reportdefinition.js to ensure the parameter is not encoded twice.
SR-C94644 · Issue 485242
Date Filter corrected for Optimized table layout
Resolved in Pega Version 8.3
The Date Filter was showing incorrect results when 'next month/current month' range filter was applied on the 31st of the month and the Allow Optimize code check box was enabled in the table layout properties. This was traced to the pySymbolicStartDate and pySymbolicEndDate properties values not being properly populated with time, and has been corrected.