SR-B6428 · Issue 280748
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.
SR-B6575 · Issue 277285
Filter popup made more efficient for large number of parameters
Resolved in Pega Version 7.3
The filter pop-up was not fully loading when the grid source has a very large number of parameters. To resolve this, the request fired in the popover initiation has been changed to pass the paramList in postData and decode it while setting params in step 2 of pzGetPopOverData.
SR-B6683 · Issue 275694
Tab layout focus corrected for "show next error"
Resolved in Pega Version 7.3
The "Show Error" and "Show Next Error" functionality in the layout group of type tab were not giving focus to the correct element when clicking the 'show next error' if an autocomplete was present. Instead, focus was given to the element whose CSS property display was set to none. To correct this, an additional filter condition has been added to ensure the expected focus.
SR-B6770 · Issue 280879
Cleanup improved for embedded page properties
Resolved in Pega Version 7.3
pyPreviousValues was retaining embedded page properties that were no longer used in pyWorkPage, causing the field level auditing to fire and write to the audit history every time the work object was updated. This has been resolved by changing the function rule pzAddHistoryMemoForScalar to remove an embedded page property in pyPreviousValues when the property is removed from pyWorkPage.
SR-B6904 · Issue 278482
Ensure CallVirusCheck is called only after populating data in UploadedFilePage
Resolved in Pega Version 7.3
Pega 7 provides the out-of-the-box extension activity Data-WorkAttach-File.CallVirusCheck which is intended to be customized with virus checking functionality to check the content of uploaded files. However, placing the activity too early in the customized process meant the check would not be correctly performed. To correct this, CallVirusCheck and the subsequent Property-Set-Messages steps have been moved to the end of the @baseclass.pzFileUploadGadget activity to ensure the existing java step populates file information on the UploadedFilePage and makes it available for the CallVirusCheck activity.
SR-B6992 · Issue 277289
Fixed default first record focus in modal repeating grid with Internet Explorer 11
Resolved in Pega Version 7.3
After upgrade, it was observed that when a repeating grid layout is opened in a modal window, the first record was selected or focused by default when using Internet Explorer 11. This has been fixed by adding a check for accessibility.
SR-B7143 · Issue 281865
Div fixed for Add button using GridAction section include
Resolved in Pega Version 7.3
After upgrade, using the "Add" button configured as a section include with pzGridAction caused UI issues. This was due to pzGridAction (@baseclass) not closing the div tag properly after calling pzGadgetInclude, and has been fixed.
SR-B7355 · Issue 277915
Actions visible in Perform harness for cases without active assignments
Resolved in Pega Version 7.3
When a stage configured with SLA did not have any active assignments, local actions could be launched from the Review harness but were not visible in the Perform harness. This was caused by the handling for cases without active assignments: virtual assignments are used to process the stage/case wide local actions, but the name of the virtual assignment page was not set and therefore not available later to fetch the local/flow actions. To resolve this, the assignment page name will be checked and set if it is empty.
SR-B7620 · Issue 290018
PopulateCaseContents activity updated
Resolved in Pega Version 7.3
The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.
SR-B7621 · Issue 278634
Activity created cases open correctly
Resolved in Pega Version 7.3
When a case was created through an activity, an error was generated when opening the case and clicking to open assignment. This was traced to an incorrect page name being passed if the primary page was different, and has been resolved by modifying the CompleteAssignment activity Step 19 to check the precondition of Page name.