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-228169 · Issue 729003

Login error messages updated

Resolved in Pega Version 8.8

Exception response messages have been updated in order to improve security around attempts to bypass operator authentication.

INC-232970 · Issue 742011

Security update for MashUp

Resolved in Pega Version 8.8

Cross site scripting protections have been updated for the LoadMashupPage activity and RedirectTo parameter.

INC-163791 · Issue 704030

Simplified default reference time calculations

Resolved in Pega Version 8.8

After a job scheduler was configured to run at Start time = 21:00:00 for Time zone = Europe/London, the scheduler determined 20:00:00 as the next start time. This was due to the calculation for the next start time using the time zone offset calculation pattern for the date and time stored in System-Runtime-Context.pxCreateDateTime, which had difficulty with changes to the time zone definition implemented in the time between the given date and today (meaning the current time) such as daylight savings time. To resolve this, the default reference time from System Runtime Context will be 'now' instead of Date(0).

INC-184964 · Issue 705932

TextMask_Encrypted rule added for use with Oracle

Resolved in Pega Version 8.8

When a property was being encrypted by propertyEncrypt access control policy and masked by propertyRead access control policy, it showed a "@@getMaskedValueOfText" error. This has been resolved with the addition of a new rule pxTextMask_Encrypted for Oracle product type which will remove extra spaces from the SOURCE string to handle ORACLE specific usecases.

INC-186897 · Issue 681030

DSS DisableAutoComplete setting honored

Resolved in Pega Version 8.8

Setting DisableAutoComplete DSS was not working as expected. This was traced to the system not being able to read the DSS value due to timing related to database startup, and has been resolved by directing the system to read the setting in PREnvironment.java instead of from the prconfig.

INC-191404 · Issue 689095

Tracer settings made configurable for queue processor

Resolved in Pega Version 8.8

An enhancement has been added to allow configuring tracer settings for the Queue Processor module.

INC-200030 · Issue 698955

Handling added for external Kafka authorization exception

Resolved in Pega Version 8.8

When using external Kafka for stream service, the dataflow was failing with the error 'QueueProcessorDataSubscriberException' when topic create permission was missing. As a workaround, the topics could be pre-created, though a "Topic already exists" warning was generated. To resolve this, the cluster-wide right that a producer needs, IdempotentWrite, has been added. For more information please refer to the link https://docs.confluent.io/platform/current/kafka/authorization.html

INC-202865 · Issue 709921

Shared partition operations performance improvements

Resolved in Pega Version 8.8

A significant performance degradation was seen in queue processor overhead related to maintaining the partition table. This has been resolved by adding an update which will improve partition operations in a shared context.

INC-205938 · Issue 721198

Improved handling for heavy use of PushDailyUserData

Resolved in Pega Version 8.8

The PushDailyUserData agent was causing utility node performance issues due to the amount of data it was fetching from pr_hourly table. To resolve this, an update has been made which will run the agent once per day and chunk large data.

INC-206288 · Issue 705267

Addressed intermittent Issues with OAuth2

Resolved in Pega Version 8.8

Issues with logging in to a node by way of the access token endpoint were related to the error "JSON web token is rejected during signature verification due to bad signature". This has been resolved by adding clock skew value to the JWT processor bean during validation.

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