SR-126031 · Issue 188833
Escape added to allow double quotes in UI read-only expressions
Resolved in Pega Version 7.1.8
In the Read only expression under the presentation tab of the properties panel for a section, including an expression which contained double quotes blocked the UI from being rendered. Upon analysis it was found that the characters were not properly escaped, and this has been fixed.
SR-126044 · Issue 189648
Rule resolution class search corrected for performFlowACallback function
Resolved in Pega Version 7.1.8
When performing an operation on a grid and then switching to local action, the thread name was being appended as undefined. This was caused by the rules search running on @baseclass instead of the framework class. A null check has been added to the performFlowACallback function to correct this.
SR-126051 · Issue 188520
External assignment goal execution corrected
Resolved in Pega Version 7.1.8
When an external assignment was created and correspondence generated to provide the external link, using Goal Execution to send a follow up was not working as expected after migration. Previously, the .CorrHandle property was stored and retrieved from the pxflow pages with a reference to the main flow which contained the External Assignment, and the "ExternalGoal" activity used the CorrHandle property to retrieve the correspondence and send a follow up. This was no longer working as the .CorrHandle property was relocated under a different page (VerifySendCorr). CorrUpdate has been modified to handle the flowname properly.
SR-126075 · Issue 192229
Added error handling for nested Tree Grid submit function
Resolved in Pega Version 7.1.8
When using a nested tree grid with a modal dialog that had a section Errors(section) from @baseclass, clicking the "save" button in the popup hid the files shown in the expanding area. This has been fixed by explicitly clearing the "partialTrigger" parameter set by the parent grid for the function SubmitModalFlowAction if there are errors in interest page.
SR-126082 · Issue 190051
Accessibility enhanced for navigating repeating grid search results
Resolved in Pega Version 7.1.8
An accessibility enhancement has been added to enable full keyboard navigation through the search results of a repeating grid in read-only mode. Double-clicking on a search result item opens the item in review mode in a separate tab, and the same functionality has been added which will open the tab by pressing the enter key on the item.
SR-126121 · Issue 189977
Improved Global Search box dismissal on iPad
Resolved in Pega Version 7.1.8
On an iPad, prforming a search with any application that shows the global search control in its header displayed a pop-up that could not be dismissed by tapping on the application below the search box. This issue occured when the script pega_desktop_AppControllerLite.js is included in the header section of the harness.To address the problem, the event binding logic for search on mobile devices has been updated to listen for a tap event instead of a click event.
SR-126181 · Issue 188742
Corrected tab display for failed visible when conditions
Resolved in Pega Version 7.1.8
When a repeating tab layout on a page group property includes "Body Visible When", tabs were displayed properly, but sections within were not being rendered for some tabs. To correct this, a visible when rule has been added to the outside content Div to handle situations where the when condition is not satisfied.
SR-126361 · Issue 189663
Case Designer modified to counter Microsoft Internet Explorer 8 UI override
Resolved in Pega Version 7.1.8
While working in the Stages & Processes tab using the Microsoft Internet Explorer 8 browser, it was not possible to view or modify the step and details and some buttons were not working. This was due to the display of auto complete being overridden with the browser's UI styles z-index. To create the proper behavior, the Case-Designer-styles CSS has been modified to add a Pega-specific z-index for process entry in Microsoft Internet Explorer 8.
SR-126368 · Issue 196112
Application Wizard node validation improved
Resolved in Pega Version 7.1.8
When using the new application wizard on a FW which has multiple built ons, selecting cases from a built-on app caused the wizard to validate the classes incorrectly and expected the user to change class names. To correct this, the application express has been updated to track intermediate class nodes that are not class groups, and now tracks non-workgroup and case type leaf name components and aggregates them.
SR-126460 · Issue 190738
Corrected persistent highlighting of work object
Resolved in Pega Version 7.1.8
If a work object was opened from the following button in the left panel, that particular WO opened but remained highlighted in blue even after other selections were made. This was caused by a configuration issue where the pyFavorites section was refreshed if the FollowUnFollow count changed, but if there was a Mixin as the Background for Row focus and Row Selection cases the text would remain highlighted until there was another change in the FollowUnFollow count. In order to resolve this, "Use default background for this format" will be enabled by default.