SR-A89158 · Issue 257328
Tuning to speed ADM thread startup
Resolved in Pega Version 7.2.2
Threads were appearing hung during ADM startup due to extended time spent loading model factories from the database into memory. Improvements have been made to reduce this loading time by changing the way in which the models are serialized to / deserialized from the database.
SR-A97899 · Issue 270052
DSM property reference handling updated
Resolved in Pega Version 7.2.2
When a complex property reference was passed to DSM page, it was treated as a simple reference and incorrect results were returned. This has been fixed.
SR-A87923 · Issue 257159
Improved logging for Data Flow exceptions
Resolved in Pega Version 7.2.2
When an error occurred on a source shape in data flow, the page information was not reported in the error report and log. This was due to a handling error that lost the reference of the original page in this scenario, and the system has been updated to improve troubleshooting by retaining the reference and including it in the error report as well as reporting it in regular logs.
SR-A25537 · Issue 256157
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-A86679 · Issue 257744
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-A88525 · Issue 257026
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-A90544 · Issue 258460
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-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