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-201648 · Issue 696965

Corrected duplicate record error message

Resolved in Pega Version 8.6.3

When inserting a duplicate record in a grid, the error was shown at the harness level instead of the record level. This was traced to the error messages being removed from the step page, and has been resolved by updating the system so messages will not be cleared if the same value is being set.

INC-201991 · Issue 692861

Explicit connectivity close added to Queue Manager error handling

Resolved in Pega Version 8.6.3

Performing a connectivity test on the MQ Connector page with an invalid queue name aborts the test connectivity but the MQ connection was not closing. This can become an issue when using IBM MQaaS (MQ as a service) where only a limited number of connections are allowed. This has been resolved by adding an explicit Queue Manager close in the error handling block.

INC-202510 · Issue 695890

SOAP connector supports OAuth2 profile

Resolved in Pega Version 8.6.3

Support has been added for using an OAuth2 profile as one of the allowed profiles for SOAP connector.

INC-202743 · Issue 697115

Cleanup added for disabled/deleted operator passivation data444

Resolved in Pega Version 8.6.3

In some scenarios, a passivated session for a non-active operator was able to be resumed after cluster restart. This has been resolved by adding a check for disabled or deleted operators which will then delete any lingering passivated data.

INC-206240 · Issue 698248

Custom headers work in MS Graph

Resolved in Pega Version 8.6.3

Custom headers were not working for MS Graph. This was a missed use case for checking headeractualname to identify whether it is a custom header, and has been corrected.

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