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.

INC-155592 · Issue 621988

httpclients library upgraded

Resolved in Pega Version 8.5.3

Package import/export was not working using prpcserviceutils, and a SSLPeerUnverifiedException" error was seen. This was traced to an issue with the third party library httpclients v4.5.9, and has been resolved by upgrading to httpclients v4.5.13.

INC-155789 · Issue 622546

Third-party libraries upgraded

Resolved in Pega Version 8.5.3

The following third-party jar files have been updated to the most recent versions:ant: v1.10.9 httpclient: v4.5.13 xercesImpl: v2.12.1

INC-157196 · Issue 629298

Deprecated service package features now require authentication

Resolved in Pega Version 8.5.3

Authentication has been added to deprecated features of the standard service package to improve security. If issues are encountered during product migration, please use the Deployment Manager.

INC-158519 · Issue 625080

Filter considers all instances pages during deployment

Resolved in Pega Version 8.5.3

During package deployment, attempting to use Filter to skip some of the instances only displayed the result of the current active page instead of all pages. This was an unintended consequence of previous work, and has been resolved by adding the logic to strip quotes in the value and adding the "Pagination activity manages filtering" checkbox by default.

INC-160288 · Issue 626068

Kerberos handling updated for database remap

Resolved in Pega Version 8.5.3

After upgrade from Pega v7.2 to Pega v8.4, using Kerberos authentication was failing during the remap task. Investigation showed that null username and password values were being passed to SchemaAssignmentUtility along with the flags as arguments, causing the utility to misinterpret the arguments. As arguments should be populated only when flags and values are available and not null, an update has been made which will set the username and password flags only if they are not null in the Remap database tables target.

INC-133951 · Issue 584149

Try catch added for templated refresh when

Resolved in Pega Version 8.5.3

After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to+F386 DynamicLayoutGenerator.java.

INC-137875 · Issue 608102

Update for special characters in operator name

Resolved in Pega Version 8.5.3

Handling has been added for encoding an operator full name field which contains special characters.

INC-139086 · Issue 597146

"Show next error" correctly displayed on user portal

Resolved in Pega Version 8.5.3

In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.

INC-139739 · Issue 598902

Cross-Site Scripting protection update

Resolved in Pega Version 8.5.3

Cross-Site Scripting protections have been updated for labels.

INC-141302 · Issue 614994

UI automation script documentation update

Resolved in Pega Version 8.5.3

To provide a more consistent experience, explanatory comments in the code for UI automation scripts have been removed.

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