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-223851 · Issue 722732

Property encryption documentation updated

Resolved in Pega Version 8.8

Documentation on encryption has been updated to clarify that Property Encrypt policies can only be created in Work- Data- , and Index class descendents.

INC-225373 · Issue 737824

Documentation updated to clarify enabling "Application data encryption" cannot be undone

Resolved in Pega Version 8.8

The documentation regarding encrypting application data has been updated to clarify that once "Application data encryption" is enabled, it is only possible to change the platform cipher from one provider to another standard or custom provider but it cannot be disabled or returned to default data settings. "Caution: After you enable application data encryption, you cannot disable it and restore the default settings. However, you can change the initial encryption type to another encryption type as necessary." "Caution: If you delete the KMS master key or the KMS master key expires, Pega Platform cannot decrypt the previously encrypted data, which can result in data loss."

INC-226047 · Issue 726468

Upgrade from Pega 6 documentation updated

Resolved in Pega Version 8.8

The documentation for "upgrading from Pega Platform version 6.3 SP1 or earlier: Starting from a single-schema configuration" has been updated to clarify that a new rules schema should be specified as the target rule schema.

INC-234290 · Issue 742941

Conversational Channel training model documentation updated

Resolved in Pega Version 8.8

Documentation for Conversational Channels has been updated with additional information about the process of creating training data based on CSR actions such as 'create a case' or 'send a reply using suggested/other replies'.

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.

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