SR-A98193 · Issue 266453
Black listed properties properly excluded from compare results
Resolved in Pega Version 7.2.2
After upgrade, properties that were included in the black list were showing up in the compare results. This was an error in determining which declaratives would be disabled when calling the applyIgnoreMap method directly, and has been fixed by removing declarative enabling / disabling from applyIgnoreMap, and moving them into the code for PageCompare.
SR-A90621 · Issue 259615
Navigation highlighting fixed for items on horizontal menu
Resolved in Pega Version 7.2.2
Highlighting was not working correctly on a horizontal menu. On clicking on the first menu, the correct window opened and was highlighted, but when opening the subsequent menus, highlighting appeared for a fraction of a second and then disappeared. This was an issue with focus not returning back and not highlighting items which were not first or last in the menu bar, and has been fixed.
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-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.
SR-A43745 · Issue 249270
Copied ticket shapes properly visible on Work Management
Resolved in Pega Version 7.2.2
After correcting a problem with the XML generated by ticket shapes related to work states, attempting to use a copied shape with Tickets resulted in a problem locating new entries in the Work Management Tickets landing page. This was an issue with the ticket details being embedded in the shape pages while the rule references that were created for the tickets in pyModifiers were not updated to match, and has been resolved by adding rule references for the tickets embedded inside the shapes.