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.
SR-D15089 · Issue 485330
Handling added for single quotes in custom DateTime controls when using Export to Excel
Resolved in Pega Version 8.3
A previously resolved issue with the timezone not being appended to datetime when exporting to Excel if a custom control was used has been further updated to better handle single-quote strings in custom DateTime controls.
SR-D13160 · Issue 485449
Hotfix installer updated to adhere to installorder file included in the package
Resolved in Pega Version 8.3
In order to ensure hotfixes are always installed in the proper order, the installer has been updated to iterate over a set that is ordered according to the INSTALLORDER.PEGA file included in the DL file at packaging time.
SR-D11911 · Issue 485465
Mobile JS performance improved
Resolved in Pega Version 8.3
Some out-of-the-box javascript bundles contained un-compacted scripts, creating a performance issue issue on mobile. This has been corrected.
SR-D16221 · Issue 485527
Email replies fixed for cases addressed to CC or BCC address
Resolved in Pega Version 8.3
Using Customer Service, if a Customer included 3 email accounts in single email (one email in To, one in CC, and one in BCC) and all three accounts had the listener configured and running, the system created 3 cases accordingly (I-1, I-2 and I-3). However, when the CSR picked up the case and replied back on each Interaction case, the customer could receive emails only from the first case (the I-1 case which was created based on To address) and replies from the other cases created from the CC and BCC email addresses were not received. Investigation showed that the function populating the “From” email address for replies was only considering email addresses in the “To” recipient list of the original email and not the email addresses which were in the “CC” or “BCC” list. This has been corrected.