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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-170646 · Issue 658308

Security update for unauthorized URL requests

Resolved in Pega Version 8.6.2

Updates have been made to improve security around unprivileged users and unregistered requests.

INC-172849 · Issue 665982

SortPageList method updated for Obj-Sort

Resolved in Pega Version 8.6.2

Sorting page lists backed by a node level datapage using Obj-Sort was causing a ConcurrentModificationException. This has been resolved by updating the SorterImpl.sortPageList method to use java7CollectionsSort instead of collectionsSortWithInferenceEngineDisabled.

INC-174625 · Issue 655243

Admin Studio will consider cluster protocol when returning listener status

Resolved in Pega Version 8.6.2

When using a few nodes in standalone mode for BIX extract combined with server nodes using Hazelcast, opening the admin studio pages with service discovery caused an error to be thrown. This was traced to the system writing an entry to pr_sys_statusnodes table as an embedded node whenever a BIX extract was triggered, causing those standalone nodes to be incorrectly considered by the listener landing page. This has been resolved by configuring the system to either return the local member when the cluster protocol is standalone or to return all Hazelcast members if the cluster protocol is Hazelcast.

INC-175672 · Issue 655810

ServicePackage thread handling improvements

Resolved in Pega Version 8.6.2

Work recently done to improve the release of requestor pool threads for the ServicePackage has been further enhanced by adding an explicit status notification to the thread waiting for Data Pages to be loaded in background and added support for the use case of a missing object handler.

INC-176112 · Issue 662449

When rule inside a loop correctly picked

Resolved in Pega Version 8.6.2

While using a 'when' rule inside a loop of a page list, the rule was not being picked during runtime. This has been resolved by adding an update to allow an assembly time class name to be passed into runtime.

INC-176903 · Issue 657339

Ready to process records count correctly displayed

Resolved in Pega Version 8.6.2

After update, the QP's ready to process records count was always shown as zero in the Admin studio QP landing page. This was traced to a missing sListMaxResultCount property in the SQL query for qp-partition retrieval; this has been added, and the default value has been changed from 0 to -1 for proper interpretation of results.

INC-177512 · Issue 657017

Hazelcast packages expanded for Java9+ with kubernetes

Resolved in Pega Version 8.6.2

Hazelcast warnings were seen in cluster logs when Hazelcast was run in embedded mode or c/s mode on a java modular environment i.e. java 9+ which noted that performance and functional impact issues may result if certain internal modules of java are not given reflection access. This update provides the necessary access to some additional java internal modules/packages per the Hazelcast recommendation.

INC-177773 · Issue 665337

Tracer protections updated

Resolved in Pega Version 8.6.2

Cross-site scripting protections have been updated for Tracer.

INC-178148 · Issue 660925

Handling added for SSO servlet name

Resolved in Pega Version 8.6.2

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

INC-178923 · Issue 660886

Resolved startup error related to business calendar object

Resolved in Pega Version 8.6.2

An error recorded in the log file when the server started was traced to a cache update that removed the old business calendar object and added the new business calendar object to the business cal list. This has been resolved by updating the system to replace the business calendar object instead of removing the old one from the cache first.

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