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-196561 · Issue 688846

Natural Language Processing (NLP) topic categorization working consistently for German

Resolved in Pega Version 8.6.4

A few German words were not recognized by the Natural Language Processing (NLP) topic categorization if they were given in capital letters. This was traced to upper case keywords being lowercased during model creation time, but not during prediction time. To resolve this, all words will be lower-cased before the model analyzes the text.

INC-206109 · Issue 706238

Delayed Learning works correctly with Volume Constraints

Resolved in Pega Version 8.6.4

When running an outbound campaign using NBA Designers predictions and delayed learning in conjunction with volume constraints, the adaptive models ended up with incorrect feedback if the prediction had an Alternative label configured with a defined waiting window. This has been resolved with the addition of a new flag 'isVolumeConstraintEnabled' during dataflow creation which will check for volume constraint, and a filter in HandleResponses for that flag.

INC-207357 · Issue 703348

Decision Management book updated for additional NLP troubleshooting

Resolved in Pega Version 8.6.4

Troubleshooting articles have been added to the Decision Management book which address the most common issues encountered when working with the NLP capability of Pega Platform, including topic and entity detection and email parser. These tips can assist with issues such as a node running out of memory due to having a large number of custom Ruta scripts that use REGEX pattern matching.

INC-208709 · Issue 710808

Added handling for new requestor in previously authenticated Voice AI group

Resolved in Pega Version 8.6.4

When attempting to pilot the new Voice AI feature set provided recently in the Customer Service framework, the error "You lack access required to execute RULE-OBJ-ACTIVITY WORK-CHANNEL-INTERACTION-VOICEAI TRANSCRIPTDISPATCHER" was logged. The same was seen for the ConnectToAudioProcessor activity. Investigation showed this could happen when a new requestor that's not authenticated yet gets created with currentAccessGroup already equal to the desired access group, causing the authentication step to be skipped. This has been resolved with an update to address the dataflow thread authentication edge case where the default requestor access group is equal to the dataflow run's access group.

INC-209294 · Issue 702711

Support added for variable queue processor partition count

Resolved in Pega Version 8.6.4

An activity called "pxAlterStreamPartitionsInternal" that is defined on Data-Decision-Streamservice- class has been added to support scaling up and scaling down stream service partitions as needed. To allow dataflow runs to automatically detect these changes and redistribute partitions accordingly, a DSS has been added: Owning Ruleset: Pega-DecisionEngine , Purpose: dataflow/run/partitions/changeDetectionFrequency , Value: 120 (default value in seconds) The dynamic system setting may be changed to -1 to disable the automatic partition changes feature, but it is recommended to leave the value set to its configured default. The following articles contain information for executing the activity: https://docs.pega.com/decision-management/87/sizing-queue-processors-and-stream-data-sets-individually-changing-number-partitions-topic https://docs.pega.com/decision-management/87/changing-default-number-partitions-topic Note: The "pxAlterStreamPartitionsInternal" activity is mentioned as "pxAlterStreamPartitions" in the above article, but the steps to execute the activity are the same.

INC-210126 · Issue 708782

Timeout added for Cassandra writes

Resolved in Pega Version 8.6.4

When using Customer Decision Hub with external C* deployment, attempting to stop a data flow run which was reporting stale threads for some partitions resulted in some of the partitions continuing to run while threads were waiting on the Cassandra save operation. This has been resolved by adding configuration for a timeout when waiting for the results of the save operation, with a default of 300 seconds.

INC-210639 · Issue 705347

Query limit removed from Scenario Planner

Resolved in Pega Version 8.6.4

Scenario Planner was not correctly finding or opening some Audience Simulations. Investigation showed that when there are 500+ completed data flows, the system was failing to load next 500 records from pegadata.pr_data_decision_ddf_runtime. This has been resolved by removing the query limits, and additional debug logging has been added.

INC-211251 · Issue 706539

Handling added for Model level Data type empty values

Resolved in Pega Version 8.6.4

After update, the Email Intelligent Virtual Assistant™ (IVA) was not able find the proper response for the real-time incoming emails but was able to find the topic and response when running it from Dev Studio and Prediction Studio. This was due to an edge case where the model datatype page list property was present on the text analyzer rule and a page was present in it, but the property pyName which actually holds the data type (body, attachment, all) was not present in the page. This has been resolved by updating the system to add 'all' as the datatype if the pyName is blank (null or empty).

INC-211349 · Issue 709605

Service API called directly in CDH simulation

Resolved in Pega Version 8.6.4

Running a simulation from the Customer Decision Hub with strategy and dataflow that used customer data resulted in with either a failed run or blank explain detail reports. Investigation showed synchronization was not triggered due to the pxVBDAvailable call returning false, and this has been resolved by directly calling the service API without additional checks.

INC-212169 · Issue 710513

Log4j file security vulnerability issue addressed

Resolved in Pega Version 8.6.4

A zero-day vulnerability was identified in the Apache Log4j logging software which could potentially allow malicious actors to take control of organizational networks. Pega has immediately and thoroughly addressed this issue. More information can be found at https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability .

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