SR-118725 · Issue 174420
Corrected focus for filter window using WAI
Resolved in Pega Version 7.1.7
With WAI enabled for work object - Audit window- History table - Time column, clicking on Filter window did not properly move the focus to the first element i.e., Add/Remove columns link. The getFirstInputElement API has been modified to fix the reported issue.
SR-D68328 · Issue 557751
Unload handler added for use with custom popups
Resolved in Pega Version 8.1.9
A memory leak seen in Microsoft Internet Explorer was traced to a custom script to close windows which bypassed window unload and continued to hold some objects in memory. This has been resolved by introducing a new file which will load only for popup harnesses and which registers the unload handler to remove the popup window references.
SR-118081 · Issue 169902
Focus correctly set for dynamic select using accessibility
Resolved in Pega Version 7.1.7
When using a cascading dynamic select control configuration with the PegaWAI accessibility ruleset, setting the focus of the first DS list did not work when attempting to navigate the UI components via the keyboard. When reaching the first DS control, users could only select the next item in the list and then the focus switched to the second DS list immediately. The DynamicSelect control was missing a name attribute, and has been updated to address the focus issue.
SR-117674 · Issue 170571
Smart Shapes use properly limited to work class
Resolved in Pega Version 7.1.7
An error in the code made Smart Shapes visible when creating a data-class flow. Attempting to include them by dragging them into the flow design pane resulted in an "empty" utility shape that was missing many of the options normally offered. Because Smart Shapes are designed only for work classes, Smart Shapes will not be visible in shape menu when a flow is created in data class.
SR-113597 · Issue 163512
Fixed ability to use 'disable work processing' in the dashboard
Resolved in Pega Version 7.1.7
Setting 'disable work processing' to true caused an NPE when opening a modal window via a Local action from dashboard (assign page class). This was caused by the process attempting to assign properties from a null page, and has been corrected.
SR-108805 · Issue 149539
Help updated to explain When Rule "ALL" Evaluation behavior
Resolved in Pega Version 7.1.7
A 'when' rule evaluating all pages in page list will only evaluate the properties on pages in the list that contain that property. This may cause a "true" result that does not match customer expectations. The hover help has been clarified to explicitly state that the evaluation results apply only for those pagelist entries where the property exists and not for all the page list entries.
SR-116805 · Issue 175879
Focus highlighting added to sub-tabs when they receive focus
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
Focus highlighting was not appearing around sub-tabs when they received focus. There was a CSS workaround for this, but it has been resolved.
SR-117428 · Issue 169351
Resolved performance issues when R-D-E referenced a data page
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
If a declare expression referenced a data page, loading or refreshing a section in update mode caused Rule-Declare-Expression to check whether inputs had changed. The R-D-E then loaded the data page (but didn't pass any parameters), causing the data page to load the max number of pages allowed. Subequently, a series of other R-D-Es fired on that data page as inputs had changed, ending up with a large number of R-D-E's firing that weren't required for a section. As a result, the elapsed time was higher than expected for every screen where this was happening and CPU consumption was high. Auto Population should only trigger on reference to a non-key and non-param property, and this has been implemented.
SR-117428 · Issue 170976
Resolved performance issues when R-D-E referenced a data page
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
If a declare expression referenced a data page, loading or refreshing a section in update mode caused Rule-Declare-Expression to check whether inputs had changed. The R-D-E then loaded the data page (but didn't pass any parameters), causing the data page to load the max number of pages allowed. Subequently, a series of other R-D-Es fired on that data page as inputs had changed, ending up with a large number of R-D-E's firing that weren't required for a section. As a result, the elapsed time was higher than expected for every screen where this was happening and CPU consumption was high. Auto Population should only trigger on reference to a non-key and non-param property, and this has been implemented.
INC-130011 · Issue 571833
Resolved stale reference error when swapping stages with drag and drop
Resolved in Pega Version 8.1.9
If user swapped stages (2nd stage to 1st stage) using drag and drop and then added a participant or role in the stage, a Pega blue screen appeared. This was traced to using a grid with reorder and an inner grid in the cell. On drag and drop, the grid reference object was stale and not in sync with the latest table. To resolve this, code has been added to reinitialize the inner grid on drag and drop.