Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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.

SR-D22170 · Issue 495575

Whitelisted RunTime_ControlPanel streams in Designer Studio development

Resolved in Pega Version 8.2.3

Using developer access in Designer Studio was generating SECU0016 errors in PDC: "Unauthorized access to the stream rule : Unauthorized access to the stream rule Data-Portal-DesignerStudio.pzRunTime_ControlPanel Rule-HTML-Section". This has been resolved by whitelisting stream names starting with pzRunTime_ControlPanel.

SR-D25607 · Issue 495622

Added NPE handling to PegaInstaller

Resolved in Pega Version 8.2.3

When upgrading, the error "Error: java.lang.NullPointerException [java] at com.pega.pegarules.deploy.internal.exposecols.jobs.ExposeWrapper.runExposer" appeared and the installation would not proceed. Investigation showed that the NPE occurred because of class name validation not being performed at the right place. As the NPE occurred in the main class, it initiated thread pool executor shutdown. However, the consumer pool did not shutdown because it did not receive the correct specific producer message fto do so. This has been resolved by ensuring isValidClass is executed at the right place in ExposeWrapper.java to handle the NPE, and adding handling for the interrupt exception in consumer thread so that in case of any run time exceptions in the main thread, the consumer thread will not be stuck.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us