SR-115000 · Issue 165234
Operator substitutions restored to the availability settings
Resolved in Pega Version 7.1.7
The operator availability setting links for Case Manager portal and Case User portal were missing substitute assignee details. These have been restored.
SR-115242 · Issue 164582
Last row delete in Grid Repeat generated an error
Resolved in Pega Version 7.1.7
If a Grid Repeat contains only one row, hitting 'delete' properly removed the row, but the java script error "this.rightBodyTbl.rows[...].cells is null or not an object" appeared. This error was caused by a missing null check inside the focusing api, and has been fixed.
SR-115268 · Issue 166797
Cleanup improved for resolved work-items
Resolved in Pega Version 7.1.7
An error in the logic for Stage Flows caused improper cleanup of resolved work items, leading to outsized assignment tables. This has been corrected.
SR-115272 · Issue 167336
Corrected clipboard mismatch for refreshed Repeating Grid pages
Resolved in Pega Version 7.1.7
When using Repeating Grid pagination in Screen Flow, refreshing the screen by choosing that option from the context menu displayed with a right-click followed by selecting 'Next' on the repeat grid caused a NPE. This was caused by a mismatch with the clipboard page, and has been corrected.
SR-115387 · Issue 166507
Flow Action support tuned for MenuBar keyboard navigation
Resolved in Pega Version 7.1.7
Using the' MenuBar' setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu: the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouse click was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected.
SR-115511 · Issue 168772
Application Express Wizard updated to correctly bind rulesets
Resolved in Pega Version 7.1.7
New Rule-Access-Role-Obj (RARO) rules created using Application Express wizard were being bound to specific ruleset versions vs. ruleset names. This caused failure to any modification to those RAROs, since modifying a RARO with a ruleset version would mean the save-as would fail if the validation found a RARO already present for that ruleset. In order to ensure proper binding and aid migration, a RARO with ties to a ruleset version will have that the version information removed automatically upon saving of the RARO.
SR-115521 · Issue 166317
Repeat Grid navigation enhanced for 'Expand Pane' edit mode
Resolved in Pega Version 7.1.7
If a Repeat Grid in a section was set to 'Expand Pane' as the Edit Mode , the 'previous' and 'next' buttons on the modal dialog were not working. The logic was missing for the Next and Previous APIs when using 'Expand Pane', and has been inserted to fix this issue. In addition, the Next and Previous APIs were enhanced to be appropriately disabled when the first and last rows are reached.
SR-115687 · Issue 165814
Vertical scrollbar fixed for expandable rows in Repeating Grids
Resolved in Pega Version 7.1.7
When using a Repeating Grid layout with pagination, expandable rows, a fixed size, and frozen header, expanding the row during run time caused the vertical scrollbar to disappear. The API has been updated to properly display the scrollbar for this setting combination.
SR-115711 · Issue 165363
Flow Action class correctly retrieved for subprocesses
Resolved in Pega Version 7.1.7
When running a Process Flow in a Data- class that is called from a Work- process flow via a SubProcess, the error "Failed to find a 'RULE-OBJ-WHEN' with the name 'CANMAINTAINCASEREPORT'" was being generated. This was caused by incorrect handling for the class: the flow action and WHEN rule are in a WORK class, but when the sub-flow is executed it looks in the DATA class of the embedded page instead of the WORK class relevant to the overall case. There was a workaround of saving the WHEN rules into the Data- classes, but the system now uses workPage instead of interestPage for localcase to ensure the correct class is retrieved.
SR-115749 · Issue 167027
Support added for custom filtering and refresh inside a Repeat Grid
Resolved in Pega Version 7.1.7
If a dropdown control was placed in the column header of a repeating grid to work as a filter and perform a section refresh for the list (based on a column present in the list, but not displayed in the grid), checking the option to freeze the column headers (and use a fixed height/width) caused the dropdown to no longer work and no refresh action could be triggered. This was caused by a second hidden dropdown in the grid with the fixed header configuration that overwrote the selected value in the ASYNC request that is sent when the dropdown value changes. To remedy this, changes were made in the HTML generation to make the hidden header input disabled. This works only when configured as "auto": the control generation logic overwrites all readonly conditions to true if the dropdown is configured as "Editable".