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-A90546 · Issue 258461

Added better handling for campaign records processing timeout

Resolved in Pega Version 7.2.2

When executing a high volume Pega Marketing campaign on a multinode system, the data flow was sometimes dropping input records if the rest of the flow was slow, leading to a stalled run where not all of the records were processed. The handling for this condition has been improved with greater tolerance to ensure all records are processed.

SR-A94009 · Issue 261505

Facebook post and comments retrieval improved

Resolved in Pega Version 7.2.2

When interfacing with Facebook, duplicate tagged posts were retrieved and comments above 100 were not incorporated. The duplicate posts were caused by the status types, and this has been updated. Comments now has pagination so all comments are properly retrieved.

SR-A97279 · Issue 275613

Resolved unneeded data flow validation error

Resolved in Pega Version 7.2.2

When selecting a data flow for a strategy test run, the error "Could not find data flow " was being logged for all the data flows available in the environment. This issue occurred when there were data flows in different applications in the system: the validation process of the smart prompt would try to load all data flows and try to validate them regardless of whether they were part of the application. While the logs did not affect functionality, the activity that executes the validation of data flows has been modified to no longer execute validation on data flows that don't belong to the current application. It will list all existing data flows and then check if it can be accessed by the current operator. However, please note that incorrect results may appear if external applications are used to monitor the logs

SR-A90366 · Issue 258967

Removed incorrect pxObjClass addition during DSM optimization

Resolved in Pega Version 7.2.2

When the DSM page optimizer flag was on, trying to adapt a platform page group property to a DSM page group property was adding a pxObjClass into the DSM page group. This caused a class cast exception from String to ClipboardPage. This extraneous addition of pxObjClass when creating an empty DSM page group property has been removed.

SR-A80606 · Issue 254964

Data Import API updated to be case-sensitive

Resolved in Pega Version 7.2.2

When using a Data Import Shape for a Class Type which had a same named property identifier (but with a different case) as in the SR hierarchy, both the properties were considered valid and imported as SR properties. This caused issues in the strategy rule as the Set property components set the values for the incorrect instance and eventually led to strategy failures as the expected instance did not have a value set. This has been resolved by using a case-sensitive API to validate the source property against the target class.

SR-A24962 · Issue 250080

DataSet-Execute updated to correct time-to-live error

Resolved in Pega Version 7.2.2

When using the time to live option of a Decision Data Store dataset, the java generation for the DataSet-Execute method was causing java compilation errors. This was due to an inconsistency between the code generation for DataSet-Execute method in an activity and the settings provided. To correct this, the algorithm used to generate the code for DataSet-Execute method has been updated to include the time to live setting and to generate correct and compilable code.

SR-A24962 · Issue 248678

DataSet-Execute updated to correct time-to-live error

Resolved in Pega Version 7.2.2

When using the time to live option of a Decision Data Store dataset, the java generation for the DataSet-Execute method was causing java compilation errors. This was due to an inconsistency between the code generation for DataSet-Execute method in an activity and the settings provided. To correct this, the algorithm used to generate the code for DataSet-Execute method has been updated to include the time to live setting and to generate correct and compilable code.

SR-A80784 · Issue 254197

Enhancement for Facebook connector retrieval

Resolved in Pega Version 7.2.2

Whenever the Facebook connector was restarted, historical posts on the monitored page were being fetched and duplicate documents were getting harvested into the DB. To resolve this, a new search parameter has been added for the Facebook connector that will receive a date as parameter for how many period/days of historical data to fetch.

SR-B6425 · Issue 275629

Scrum Board chicklet error resolved

Resolved in Pega Version 7.2.2

After collapsing and expanding a user story chicklet in the Scrum Board, adding a new note to the user story would cause the user story chicklet to disappear. This was a rendering issue due to an error in the type property syncing with the level property, and has been fixed.

SR-A77119 · Issue 255525

Fixed attaching files to pre-existing inflight cases after upgrade

Resolved in Pega Version 7.2.2

After upgrade, loading pre-existing inflight cases and attaching a file generated the error "Trying to save an invalid page: Trying to save an invalid page: page is not valid ". This was caused by a missing check for LinkPage.pyMemo if LinkPage.pyCategory is not set, and has been fixed by setting pyMemo from LinkPage.pyMemo.

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