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-B6669 · Issue 279329
XSS filters added to UI rulesets
Resolved in Pega Version 7.3
XSS filters have been added to pyCaseActionArea and pyAssignmentsLabel in Pega-EndUserUI and UIKit rulesets.
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-B6704 · Issue 289314
Auto-populate updated for better page copy references
Resolved in Pega Version 7.3
After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.
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-B6971 · Issue 285310
Error propagation corrected for RDB-Save with RunInParallel
Resolved in Pega Version 7.3
If several Connect SQLs were called via the RDB-Save activity method with RunInParallel selected, failure of one of the Connect SQLs was not being caught and no errors were captured. This was traced to a situation where an exception thrown at the childcase with this combination of settings was propagated to the parent, and has been corrected by adding a Data-Admin-System-Setting "isPropagateExceptionFromChildToParent" defined in "Pega-RULES" ruleset, which has a default value of "true" only for RDB-Save method (not for all RDB-methods).
SR-B6971 · Issue 279537
Error propagation corrected for RDB-Save with RunInParallel
Resolved in Pega Version 7.3
If several Connect SQLs were called via the RDB-Save activity method with RunInParallel selected, failure of one of the Connect SQLs was not being caught and no errors were captured. This was traced to a situation where an exception thrown at the childcase with this combination of settings was propagated to the parent, and has been corrected by adding a Data-Admin-System-Setting "isPropagateExceptionFromChildToParent" defined in "Pega-RULES" ruleset, which has a default value of "true" only for RDB-Save method (not for all RDB-methods).
SR-B6980 · Issue 278169
fixed naming in multiple extracts run from the command line
Resolved in Pega Version 7.3
When running multiple comma separated extracts at a time using command lineoption -i, all of the rules in the manifest file contained the value of the last extract name only. This was a missed use case, and ExtractImpl has been modified to correct it.
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.