SR-B16331 · Issue 303039
Check added to WorkUnlock to ensure cover page exists
Resolved in Pega Version 7.3
An intermittent error was logged related to workunlock. This was caused by Work-.Close calling workUnlock from the param.coverPage without performing a check first to ensure that the coverPage exists and has a class. To fix this, the WorkUnlock activity has been modified to verify that the coverPage has a class before unlocking the cover object.
SR-B16331 · Issue 294717
Cover page check added to Work-Close
Resolved in Pega Version 7.3
An intermittent stack trace was being generated in Work-Close; this has been resolved by adding a check to ensure that the coverPage exists and has a class.
SR-B16784 · Issue 287160
Attachments removed when work object withdrawn
Resolved in Pega Version 7.3
After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.
SR-B17100 · Issue 290607
Optimistic locking fixed for GetNextWork
Resolved in Pega Version 7.3
The optimistic locking feature was is not working as expected when GetNextWork was invoked. This was caused by missing parameter passing, and has been fixed.
SR-B1734 · Issue 272443
Added content to blank headers for screen readers
Resolved in Pega Version 7.3
The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.
SR-B1734 · Issue 272039
Added content to blank headers for screen readers
Resolved in Pega Version 7.3
The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.
SR-B2595 · Issue 274239
Enabled process cleanup for change stage shape
Resolved in Pega Version 7.3
When using the "Approve\Reject" step in case designer on a flow containing logic to jump back to a previous stage on rejection, the system created the new assignment needed for jumping back to the previous stage but did not clean up the existing assignment. This caused two parallel flows at the same time and the old assignment was loaded on the screen. This has been fixed by enabling the CleanUpProcesses parameter in the Change stage shape function of pzPostApprovalActions.
SR-B30410 · Issue 294913
Report drilldown works with 'do not display group headings'
Resolved in Pega Version 7.3
When sub-report properties were used in the main reports column source, the report definition displayed the expected results when clicking on a configured drilldown report and chart but displayed no results when listview dataset was clicked. This was traced to having "Do not display group headings" enabled in combination with drilldowns, and has been resolved.
SR-B30438 · Issue 292802
Audit window close button function change
Resolved in Pega Version 7.3
If an Audit--View history action was configured on the KYCWorkActionsPerform navigation rule, the link worked as expected from the case manager portal but generated an error if 'audit from other actions' was used and closed before accessing the link. This was due to the close button invoking the doclose function that clears the pyworkpage. To resolve this, the Advanced/history attachments tab close button will instead invoke self.close() .
SR-B30713 · Issue 296998
New activity pyCustomValidator added to pzValidateCustomFilterSection
Resolved in Pega Version 7.3
When a report definition enables "Prompt for filter changes before displaying report", and the report specifies a custom filter section, the harness that displays the custom filter section (pzRRDisplayCustomFilterSection) is Final and was not available to validate the fields in the custom filter section. To enable this use, a new available activity "pyCustomValidator" has been added and can be called from pzValidateCustomFilterSection.