SR-D22437 · Issue 492856
Handling added for Pagelist Reference Property in LegacyPageAdapter getMode API
Resolved in Pega Version 8.2.3
Post upgrade, a "Component Stack Mismatch" error appeared while opening a work item containing an embedded section that used a Data Page D_WorkApprovalCase input parameter as the Page Context. This was traced to an exception thrown by the getMode() API invoked on an auto-populate property because the property was in a read-only data page. By default, read-only data pages are light weight clipboard pages, but auto-populating properties on light weight clipboard pages was not handled via the failsafe page in the getMode() API. This has been fixed by adding handling to the getMode API of LegacyPageAdapter for properties not supported by redux ( eg: reference, autopopulate properties etc).
SR-D22175 · Issue 493193
Null check added to control_multiselect
Resolved in Pega Version 8.2.3
After upgrade, Multiselect control was not working in some classes. The values were getting loaded into the clipboard, but on clicking the down arrow none of the values were getting populated. This has been resolved with the addition of a null check in the control_multiselect file.
SR-D22858 · Issue 493329
Checks added for case resolution based on dependencies
Resolved in Pega Version 8.2.3
Post upgrade, using a design with a wait shape configured to resolve the Parent case when all the child cases were Resolved-Completed was not working. This was traced to the handling of the page dependencies in TopCaseWork, and checks have been added to ensure correct case resolution.
SR-D23611 · Issue 493422
Autocomplete dropdown scrolls with screen rather than remaining fixed
Resolved in Pega Version 8.2.3
On selecting dropdowns(autocomplete), if the dropdown list was left open and the screen was scrolled, the dropdown list did not move with the scroll but rather remained fixed to the screen. This has been resolved with the addition of scroll handlers which will attach the popover results to its parent while scrolling.
SR-D23360 · Issue 493464
Email reply with same attachment name correctly processed
Resolved in Pega Version 8.2.3
When an email reply was received with an attachment using the same name as one received earlier, the new attachment was not getting processed and the message 'The Specified file/folder already exists in the target repository. Please specify a different file/folder' appeared. This was traced to an incomplete check for the object class that did not qualify the attachment name for a reply, and as been corrected.
SR-D23417 · Issue 493543
Image Attachment File Type error localized
Resolved in Pega Version 8.2.3
Localization has been added to the error message generated when an unsupported image is uploaded while in live-chat.
SR-D24950 · Issue 494564
Added explicit step page to resolve NPE with custom error message
Resolved in Pega Version 8.2.3
A null pointer exception was generated during case run time harness refresh after a custom error message was inserted. This was traced to a blank step page related to the custom message, and has been resolved by adding a primary step page at step 10 of the New(Work-) activity to prevent the NPE on harness reload.
SR-D26101 · Issue 495206
Improved DX API page reference handling
Resolved in Pega Version 8.2.3
When using a property that was being referred through a secondary page that could be referred directly by the case (such as .AccountClosureDetails.ClosingAccountApplicant), the page was not initialized and the local list values were not returned by the DX API. This has been resolved by improving the handling for embedded page references via section include where the property reference is a full path.
SR-D26334 · Issue 495320
Restore delegated rules short description header
Resolved in Pega Version 8.2.3
For delegated rules like SLA/Correspondence, the short description was not getting displayed in the header. This was an unintended side effect of work done on automation rule capabilities, and has been resolved by restoring the layout visibility condition pzDelegateHeader in pzRuleFormKeysAndDescription.
SR-D18036 · Issue 495397
Holdability flag set on connection for using MS SQL in Designer Studio
Resolved in Pega Version 8.2.3
Static assembler was not working from Designer Studio, displaying the error "com.microsoft.sqlserver.jdbc.SQLServerException: SQL Server supports holdability at the connection level only. Use the connection.setHoldability() method." Investigation showed that ApplicationAssembly.getResultSetForQuery explicitly sets the holdability flag on the prepared statement, and this issue has been resolved by updating the system to set the holdability flag on connection as well.