SR-B12993 · Issue 285730
Property change tracking updates for source shapes and ClipboardPageAdapter
Resolved in Pega Version 7.3
OnChange and Declare Expression rules were unexpectedly triggered during data flow executions that converted clipboard pages from DSM to regular implementation. The triggering also intermittently occurred when loading data from different dataset types while populating the page. This was traced to the handling of property change tracking, and the system has been updated so that source shapes and ClipboardPageAdapter will not track property changes.
SR-B13016 · Issue 284134
Report title shows for exported Excel; display report label name reverted
Resolved in Pega Version 7.3
Exported Excel reports were not showing the report title if the "display report filters" checkbox was unchecked in the RD rule. If the box was checked, the report title turned up in the Excel sheet, but the report UI showed an unnecessary blue bar if none of the filter criteria were set to be displayed as per business needs. The missing report title was traced to an error in the "display report filters" checkbox, and has been fixed. Additionally, the 'display report header' label in the pzReportViewerUserActions section had been recently modified to read 'display report filters', which was misleading - that change has been reverted.
SR-B13020 · Issue 283559
Upgrade App Schema generates unique index name IDs
Resolved in Pega Version 7.3
Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.
SR-B13020 · Issue 283078
Upgrade App Schema generates unique index name IDs
Resolved in Pega Version 7.3
Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.
SR-B13040 · Issue 293380
Improved reliability for GetReference API
Resolved in Pega Version 7.3
A sporadic issue with the OOB getReference API caused a failure in obtaining the absolute reference for a parameterized data page. This was caused by a race condition in the page handler, and synchronization has been improved to ensure the proper name will be set into the data page.
SR-B13040 · Issue 293526
Null DPI check added for async page load
Resolved in Pega Version 7.3
A null pointer exception was being generated when a data page was being loaded from the asynchronous cache and some exception occurred while switching the access group or getting a definition. To avoid this, a check has been added for a null DPI.
SR-B13088 · Issue 287632
SLA correctly reset after reassignment
Resolved in Pega Version 7.3
When the SLA values were updated on routing the task, the newAssignPage and assign table were updated with the new SLA details but the pxFlow page was still holding the old SLA values. This caused the updated SLA details to not be displayed in the out-of-the-box pyAssignmentListGadget section. This was an issue with the pxAdjustSLA and Reassign activities not completely updating the embedded page pxFlow in the WorkPage completely, and has been fixed.
SR-B13315 · Issue 284499
Accessibility updated for flow action label
Resolved in Pega Version 7.3
Accessibility tools such as JAWS were not reading out the flow action label. This has been fixed.
SR-B13315 · Issue 284499
Accessibility updated for flow action label
Resolved in Pega Version 7.3
Accessibility tools such as JAWS were not reading out the flow action label. This has been fixed.
SR-B13418 · Issue 283237
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'.