SR-B6244 · Issue 277565
Documentation and log messages updated for BIX/useHistoryClasses
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, messages from the system gave the impression that some of the records were skipped. This was due to a mismatch in the number of records reported at different points in the extraction: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To avoid this confusion, the text in the logs has been clarified to read: "Processing Class class name with XXXX instances (processing count may vary as records get modified before BIX extraction)." In addition, the documentation regarding the usage of the BIX/useHistoryClasses option has been updated to reflect this information.
SR-B6244 · Issue 277566
Documentation and log messages updated for BIX/useHistoryClasses
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, messages from the system gave the impression that some of the records were skipped. This was due to a mismatch in the number of records reported at different points in the extraction: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To avoid this confusion, the text in the logs has been clarified to read: "Processing Class class name with XXXX instances (processing count may vary as records get modified before BIX extraction)." In addition, the documentation regarding the usage of the BIX/useHistoryClasses option has been updated to reflect this information.
SR-B6288 · Issue 281534
Resolved agent schedule skipping a day in some conditions
Resolved in Pega Version 7.3
When a schedule was set to recurring for specific days at a certain time, restarting the system or changing the agent schedule close to midnight from a different time zone caused the schedule run time to skip a day. This was traced to a mis-match in the calendar runtime calculation logic between the time zone and the time being set when the agent and server are configured to run on different time zones, and has been corrected.
SR-B6292 · Issue 276738
New accessibility control for adding explicit text to RB column headers
Resolved in Pega Version 7.3
In order to create report browser column headers with explicit text for accessible users, a new available control named pyReportBrowserControl that uses the parameter "Type" has been added to the pzRBShortcutsGrid7 section.
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-B6500 · Issue 276002
Mobile performance improvements for static content load
Resolved in Pega Version 7.3
Performance improvements have been made for mobile by enabling concurrent parallel load of static content.
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.