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.

SR-D51017 · Issue 517182

Expanded date format handling

Resolved in Pega Version 8.4

The xx in the xx:yy time format was incorrectly detected as a year. To correct this, support has been added for the use case of the date followed by time.

SR-D52051 · Issue 515376

Corrected EditElement disappearing after DDR import

Resolved in Pega Version 8.4

After importing a DDR to a 'treatment', the section disappeared. Because the treatment decision data rules are created in the top level SR class, when the treatments are exported from these rules, the pyIssue and the pyGroup classes are empty in the exported CSV. When new treatments were added or existing treatment are modified in the CSV and imported, the pxObjClass for the treatments was set to Data-pxStrategyResult as the pyIssue and pyGroup were empty in the imported CSV. To correct this, pySelectedClass will be set to the propositions instead of pxPage.pxObjClass while importing.

SR-D52723 · Issue 516092

Data join conditions representation updated to avoid overwrite

Resolved in Pega Version 8.4

After upgrade, a Data join component on the Strategies was not working as expected, especially the ones using the DateTime function. If the data join conditions were swapped, i.e the DateTime function was not the last criteria, the strategy outputs were correct.Investigation showed that the implementation used a map to represent pairs of left and right expressions which caused conditions rows with the same leftExpr to end up overwriting one another. This has been corrected by fixing the representation of conditions of a Data Join to a list of tuples which eliminates the possibility of one condition overwriting a previous one.

SR-D53223 · Issue 516918

Predictor handling updated for Versioning Adaptive Model

Resolved in Pega Version 8.4

When attempting to update an adaptive model in a branch after it had been versioned, errors were observed on Predictor Type data that had not changed from the previous version. This was traced to an issue in the Adaptive Model rule UI in both Prediction and Dev Studio where if a non-default predictor type is selected, it would show in the UI but not be saved to the database. No error was shown. This silently led to the unexpected and incorrect data being stored with the result that once data had accrued, the rule could not be saved/saved-as due to validation believing the predictor type of a predictor with data was changing. To resolve this, rules have been updated so that the system will no longer override the predictor type of a predictor being edited when it is solely the predictor type that is changing.

SR-D53225 · Issue 516318

Rule creation logic updated to include creation branch

Resolved in Pega Version 8.4

When trying to create a new adaptive model rule in Prediction Studio, the “Create” button was not activating. The adaptive model rule was being saved in a branch ruleset, and investigation indicated that the deactivated button could be traced to the lack of an open ruleset version available even though the intention was to create it on a branch. This has been resolved by modifying the rule creation logic to incorporate the branch for creation.

SR-D53622 · Issue 515545

Dataflow Batch performance improvement

Resolved in Pega Version 8.4

Performance issues were seen when running Dataflow Batch with Interaction History lookup. This has been resolved by refining the logic used in the pzIHExecuteSQL function.

SR-D53933 · Issue 525601

Modified VBD insertion logic to improve handling

Resolved in Pega Version 8.4

An issue with not being able to launch an additional VDB node was traced to two processes inserting into VBD with different field signatures and triggering unnecessary object creation. This was amplified when adding a second node as the objects were serialized. To resolve this, the insertion logic has been modified to avoid creating new data container/field descriptors after a new field is included, as well as a measurement with smaller data type than previous container.

SR-D54218 · Issue 518601

Deadlock in static Initialization of IntList resolved

Resolved in Pega Version 8.4

JVM Deadlock was seen related to the static Initialization of a subclass field in class com.pega.decision.strategy.ssa.runtime.collections.api.IntList . Thread dumps showed threads in RUNNABLE State that were parked to wait for class initialization, and this was traced to a missed sonar alert which failed in multi-threading. To resolve this, the system handling has been updated to prevent potential deadlock.

SR-D54430 · Issue 518291

Updated VDB Statistics rendering to compensate for Google Chrome changes

Resolved in Pega Version 8.4

The Statistics overlay was not rendering for VBD planner in Google Chrome. Investigation showed that the Google Chrome browser (v.77) was misfiring one of the mouse events due to changes in the browser, and the handling has been updated to resolve this issue.

SR-D54602 · Issue 517309

Prconfigs added to support Cassandra Speculative Based Execution

Resolved in Pega Version 8.4

In order to achieve high availability for Cassandra, prconfigs have been added to support speculative execution. The available prconfigs will enable it, and set maximum number of executions and delay before the next execution is launched.The prconfigs are: dnode/cassandra_speculative_execution_policy dnode/cassandra_speculative_execution_policy/max_executions dnode/cassandra_speculative_execution_policy/delay

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