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-A91240 · Issue 259814
Corrected mobile app login load stream error
Resolved in Pega Version 7.2.2
In some circumstances, a "Failed to load stream" error was appearing when attempting to log in on the Mobile App. To fix this, the login process has been made more robust with the addition of the isSyncProcessingInProgress function to check sync progress, and a check has been added for the panel harness being set in the HCLoadManager js.
SR-A91480 · Issue 259296
Datarepeater honors user-set global dirty flag
Resolved in Pega Version 7.2.2
In pzpega_desktop_datarepeater JS and pzpega_ui_template_datarepeater JS, the code for add and delete functions was overriding the global dirty flag, creating unexpected results. The system has been updated to honor the global dirty flag if it is already set and set it only when it has not been set by the user.
INC-146564 · Issue 607856
DX API returns application specific validation messages
Resolved in Pega Version 8.5.2
When trying to validate the input swagger details with application specific conditions, the create case DX API did not return the validation messages from application but instead returned a "500 Internal Server Error". Investigation showed that the error parameter was not set on validation fail, and this has been corrected.
INC-152442 · Issue 616668
Check added for Create Access to attachment
Resolved in Pega Version 8.4.4
After restricting access for the attachments category in a CS application, the attachment was added without category and could not be opened. This was due to the Create Attachment access not being automatically created for all categories when privileges were added, and has been resolved by adding a step to check Create Access for attachments of the respective category.
INC-154564 · Issue 617350
JAWS reads the table header and filter options separately
Resolved in Pega Version 8.4.4
When table headers for a non-optimized table with filter options received focus in Google Chrome, JAWS read the header, sort and filter options all run together. This was due to a difference in the way JAWS reads headers in Google Chrome from the way it reads them in IE, and has been resolved.
SR-C57881 · Issue 402879
Localization support added for page level properties
Resolved in Pega Version 8.1.1
When trying to change the out-of-the-box pyMessageLabel "This field may not be blank.", the changes were applied at the property level but were not applied at the page level. This was due to Localizations not being handled properly at page level, and the HarnessErrorList rule has been updated to correct this.