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.

SR-D78940 · Issue 542925

Dataflow monitoring enhanced

Resolved in Pega Version 8.3.2

Enhanced monitoring and healthchecks have been added for dataflow and alerts.

SR-D79145 · Issue 543053

Added tokenizer for KeyWord-Based Topic Detection phrases

Resolved in Pega Version 8.3.2

KeyWord-Based Topic Detection was not Working for "Enrollment/Re-Enrollment" as a word, for example a categorization model with the text 'This is an email related to Enrollment/Re-Enrollment'. To facilitate this use, a tokenizer has been added to break should, must, and and words into components for a taxonomy match.

SR-D79909 · Issue 542243

DDS added for automated dataflow run cleanup

Resolved in Pega Version 8.3.2

During a recent upgrade it was seen that there were in excess of 20k dataflow runs, some 2 years old, which slowed down the migration significantly. In order to resolve this, an automated process has been added. This clean-up procedure deletes all the single case, batch, and real time runs older than 30 days which are in the final state - Completed, Completed with Failures, or Failed, and batch and real time runs which are in the Stopped state. The DDS Pega-DecisionEngine.dataflow/run/maxDaysToKeepRuns.should be used configure the retention period. Note that the retention period is calculated since the last processed message and not the creation time of the run.

SR-D82895 · Issue 543605

Restart issue on dataflow service nodes resolved

Resolved in Pega Version 8.3.2

A high percentage of rolling restarts were failing for nodes hosting dataflow services due to prolonged restart times. To resolve this, the system has been updated so Cloud services will not try to recover the node state in case of a restart, since nodeIDs are always new and not reused.

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