SR-A4972 · Issue 211383
Report Viewer remains active after launching tab Is closed
Resolved in Pega Version 7.1.9
If Report Viewer was opened from Dashboard, it shared the Dashboard's thread and would not be operational if it remained open after the Dashboard tab was closed. This was expected behavior, but the need has been established for allowing the Report Viewer to continue working independently of the Dashboard after launch, so an enhancement has been added that will now launch the report within a dynamic container so it will continue to be available after the Dashboard is closed.
SR-A4972 · Issue 211536
Report Viewer remains active after launching tab Is closed
Resolved in Pega Version 7.1.9
If Report Viewer was opened from Dashboard, it shared the Dashboard's thread and would not be operational if it remained open after the Dashboard tab was closed. This was expected behavior, but the need has been established for allowing the Report Viewer to continue working independently of the Dashboard after launch, so an enhancement has been added that will now launch the report within a dynamic container so it will continue to be available after the Dashboard is closed.
SR-A597 · Issue 206995
Removed Prompt for Filters option for Report Definition
Resolved in Pega Version 7.1.9
An issue was reported where the cancel button was not working when Report Definition included the option 'Prompt for filter changes before displaying report' and the Filter Criteria form popped up. The Add Filter option appeared briefly in the product, but is now deprecated and has been removed.
SR-A670 · Issue 206617
Removed XML display on click of row in report definition
Resolved in Pega Version 7.1.9
While using a custom section with a button to run an activity in the report definition, on clicking of the button the work object XML page was displayed along with the activity. This happened when a custom section id was specified for row display and getRowKey was enabled, causing the click of the row to open a pop-up without any rule. This has been fixed by modifying the JS code in report_events.js to avoid this pop-up.
SR-A670 · Issue 206324
Removed XML display on click of row in report definition
Resolved in Pega Version 7.1.9
While using a custom section with a button to run an activity in the report definition, on clicking of the button the work object XML page was displayed along with the activity. This happened when a custom section id was specified for row display and getRowKey was enabled, causing the click of the row to open a pop-up without any rule. This has been fixed by modifying the JS code in report_events.js to avoid this pop-up.
SR-A692 · Issue 205611
Resolved duplicate portal open when using Microsoft Internet Explorer 11
Resolved in Pega Version 7.1.9
When using Microsoft Internet Explorer 11, trying to access the My Group tab in the links 'Manage Operator Schedules and Profiles' was not displaying the screen correctly on click of any operator or workbasket and an extra portal window was opened. This was a browser-specific dynamic container issue where the lack of an explicit type=button declaration was causing a form submit that triggered a main page refresh. That declaration has been added.
SR-A734 · Issue 205406
Added null clipboard check for Recently Resolved report
Resolved in Pega Version 7.1.9
While running the Recently resolved report, a null ContentPage caused an NPE and prevented the output of the report. This has been resolved by adding a null check for the clipboard page.
INC-119669 · Issue 562586
Special character handling added to filters for table sourced with parameterized RD
Resolved in Pega Version 8.2.7
Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.
SR-D56590 · Issue 525300
Notification option for change of search nodes removed from Cloud
Resolved in Pega Version 8.2.7
The search landing page for Pega Cloud was displaying a checkbox to enable sending automatic emails if the search node was modified. As the description of the notification 'Notify on change of search host nodes' suggests, this option is to send notifications only when a search host node has been modified(addition/removal) from the search landing page. This is not applicable for the automatic addition/removal of search nodes that happens on starting the node. As the addition/removal of nodes is not allowed from the search landing page on Cloud environments, this option is not applicable for Cloud and the checkbox has now been removed for that environment.
SR-D81496 · Issue 547169
Data Social tag class FTS index query improvements
Resolved in Pega Version 8.2.7
A query intended to select from the link tag table to see if any cases were linked to the tag in question and then index the tag change was causing performance issues. Investigation showed that checking tag associations during FTS indexing fetched all matching rows from the table even though one was sufficient. To resolve this, the query will be created with max result count = 1, fetching up to 2 rows from the table.