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-217991 · Issue 714332

Display of 'check all' check box made configurable

Resolved in Pega Version 8.8

A new overridable 'when' rule pyShowSelectAllCBInSurvey has been added to allow customizing a survey to hide the 'Select all' checkbox in the ComplexQuestionCheckboxTemplate section.

INC-218145 · Issue 715679

DSS introduced to control DSM clipboard page serialization

Resolved in Pega Version 8.8

When using a Kafka dataset to consume a message from an external topic that had an attribute name with a special character contained in a page list structure, using a JSON data transform for the mapping in a realtime dataflow resulted in the error "Exception in stage: KafkaDS; LegacyModelAspectInvokableRuleContainer.invoke-Exception encountered a :java.lang.UnsupportedOperationException." To resolve this, a new DSS dataset/CLASS_NAME/DATASET_NAME/JSONDataTransform/deserialization/useDSMPage has been introduced. When the value is set to true, the process will follow the previous behavior of DSM clipboard pages being generated when Kafka records are deserialized using JSON data transform. When the value is set to false, the JSON data transform will generate regular clipboard pages and convert them later to DSM clipboard pages. This would avoid errors when a JSON data transform calls methods from the Clipboard API that are not implemented by DSM pages. This DSS is set per data set instance. CLASS_NAME and DATASET_NAME are placeholders which should be replaced by data set's pyClassName and pyPurpose property values. In addition, a similar DSS, dataset/CLASS_NAME/DATASET_NAME/JSONDataTransform/serialization/useDSMPage, has been introduced for serialization.

INC-218757 · Issue 714552

AESRemote updated to be asynchronous

Resolved in Pega Version 8.8

The Autonomic Event Services (AES) agent PushCDHMetrics became stuck and was not pushing metrics to the console. This has been resolved by updating AESRemote to be asynchronous.

INC-218909 · Issue 715281

Override added to delete records for a stream dataset after processing

Resolved in Pega Version 8.8

Kafka data was accumulating for a Stream data set due to huge volume of inbound calls. This has been resolved by adding support to override pyDeletedProcessed through a DASS in order to remove the records for a particular stream dataset (topic) as soon as they are processed by Pega.

INC-220622 · Issue 680790

Deprecated Libraries

Resolved in Pega Version 8.8

The following library dependencies have been deprecated, excluded, and/or removed: - ant - bsh - commons-compress - gson - htmlunit - io.netty - jackson-mapper-asl - jdom - jdom2 - jdom-legacy - jetty-http - jetty-io - jetty-server - jetty-util - junrar - logback-core - netty-handler - plexus - plexus-utils - xercesImpl - xstream

INC-220622 · Issue 695948

Updated Libraries

Resolved in Pega Version 8.8

The following libraries have been updated to the most recent version: - commons-collections - cxf-rt-rs-security-oauth2 - derby - dom4j - esapi - google-oauth-client - groovy - h2database - jackson-databind - java-sdk-s3 - Jcommander - json-smart - nekohtml - netty-handler - postgres - snakeyaml - spring - spring-core - underscore - woodstox - xmlsec

INC-220642 · Issue 717032

Updated context handling for executing data transforms in dataflows

Resolved in Pega Version 8.8

When performing a sort operation in a data transform on a pagelist and invoking the Data transform through a Data flow, a java.lang.UnsupportedOperationException was generated on the sort step even though the data was correct. Investigation showed that the dataflows were using a different execution context than the context used for regular activity execution. An update has been made to ensure the correct context is being used while executing data transforms in dataflows.

INC-220893 · Issue 728488

Errors persisted for single case runs using a custom error handler

Resolved in Pega Version 8.8

Single case processing (SingleAccountData) had failed records when opening the SubscriptionData dataset, but it was not possible to see the failed record details for further investigation. Investigation showed that when running a single case run with a custom error handler, errors were persisted as part of the dataflow metrics, but not written to the database. To resolve this, an update has been made to ensure errors are persisted for single case runs configured using a custom error handler.

INC-222561 · Issue 721041

Check added for destination type for distribution test reports

Resolved in Pega Version 8.8

When there were two output destinations in the system, one of type VBD and another of type Database table and both had the same name, an incorrect class was set for distribution test reports and an error was generated when trying to open the report. Investigation showed the system was only checking for the name of the destination and not its type; this has been resolved by adding a pzSetSimulationOutputClass data transform to check for the destination type in addition to the destination name when setting the class for reports.

INC-225257 · Issue 730293

Pega DateTime supports pre-1970 timestamps

Resolved in Pega Version 8.8

The function getTimeStampAsDateStamp from Pega DateTime class was not working correctly for dates before Jan 1st, 1970. Support has now been added for this use.

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