SR-B36743 · Issue 293937
BLOB data save performance improved
Resolved in Pega Version 7.3
In an installation with many large work objects, performance issues were seen when saving a BLOB. This was due to the BLOB still saving data for properties that had been removed, and has been resolved through better tracking of orphan entries of list type properties like string list and java object list.
SR-D79266 · Issue 544531
pyStatusWork for parent case correctly resolved
Resolved in Pega Version 8.1.8
pyStatusWork was not getting updated for the parent case even though the case passed through the resolution stage. This was an unintended side effect of work done regarding resolving a subcase if it was opened from the review harness, and has been resolved by updating the findPageByHandle activity to return the correct page when there are multiple pages with the same key.
SR-D64244 · Issue 532981
Support added for recording with sIngle-option radio button inside a repeating grid
Resolved in Pega Version 8.1.8
Recording a test case was not working when a single option radio button (i.e., radio button control with property of type boolean) was configured inside a repeating grid. In this case, it was found that the Radio button markup did not have a data-test-id attribute for non-template single option; this has been added.
SR-B14866 · Issue 285387
ClipboardPageAdapter retains pxObjClass values in page-lists
Resolved in Pega Version 7.3
When adapting clipboard pages from Pega Platform pages to DSM pages, the ClipboardAdapter was reverting page-list items to the obj-class defined on the property instead of keeping the actual class. This was traced to an issue with the conversion method between DSM pages and regular ClipboardPages, and has been fixed.
SR-B14866 · Issue 275830
ClipboardPageAdapter retains pxObjClass values in page-lists
Resolved in Pega Version 7.3
When adapting clipboard pages from Pega Platform pages to DSM pages, the ClipboardAdapter was reverting page-list items to the obj-class defined on the property instead of keeping the actual class. This was traced to an issue with the conversion method between DSM pages and regular ClipboardPages, and has been fixed.
SR-B33991 · Issue 292845
Corrected ability to hide filters for Export to PDF
Resolved in Pega Version 7.3
The "Display report filters" check-box was not being honored on export to PDF, causing the filters to always be shown. This has been corrected with an added visibility condition to show or hide a filter section based on the value of .pyDisplayReportHeader, and a check has been added in "RRBodyDiv" HTML rule to show header only when pyDisplayReportHeader is true.
INC-161463 · Issue 638001
Case Dependency corrected for different access groups
Resolved in Pega Version 8.6.1
Creating a queue item as part of the case dependency was not working as expected when the access groups of the dependent cases were different. Investigation showed that in this scenario, the logic was looping differently and the DependencyList page in pxCheckFlowDependencies was getting removed. To resolve this, the DependencyList page has been moved so it is processed inside the DependencyList.pxResults loop.
SR-D60375 · Issue 527755
Resolved upgrade SqlSyntaxErrorException
Resolved in Pega Version 8.1.8
When trying to perform an in-place update, the error "SqlSyntaxErrorException" appeared. Investigation showed that DDL statements for Adding 'pzInsKey' as PrimaryKey for Tables pc_work and pr_sys_locks were generated during the upgrade while pzInsKey was already the PrimaryKey in corresponding tables. This has been corrected.
SR-D74057 · Issue 540059
Updated aria handling for Dynamic Layout Group 'Accordion'
Resolved in Pega Version 8.1.8
The Dynamic Layout Group display type 'Accordion' was not getting initialized properly on the browser developer inspector. This was traced to the aria-selected attribute set to always be true, and has been resolved by adding logic to set and unset aria- selected only on the active tab. When the tab is not active, then aria-selected will be false.
SR-B12026 · Issue 283561
Overridden data flow with RD partitioned key fixed
Resolved in Pega Version 7.3
A validation error was thrown and data flow activation failed for an overridden data flow with a RD partitioned key. This was traced to the circumstanced pzValidateRuleExistance (triggered when the dataflow shape was overridden) trying to open the property rule with pyPurpose set to rule name whereas the actual property should have been pyPropertyName. This has been fixed.