SR-A2313 · Issue 207691
"int" added to pzCheckCompatibilityOfColumnTypes
Resolved in Pega Version 7.1.9
If a report definition was created with a sub-report that is joined on a column of type integer, it was not possible to save the report definition rule if one of the columns mapped to a MS SQLServer column of type int. This was a problem with the int case not being handled in pzCheckCompatibilityOfColumnTypes, and has now been fixed.
SR-A3897 · Issue 209254
Resolved authentication requirements in activity pzSetQueryDefaults for SSO setup
Resolved in Pega Version 7.1.9
Code-Security.InitialProfileSetup does not need authentication to run, but during the SSO login it calls Code-Pega-Requestor.pzSetQueryDefaults which was hard-coded to require authentication. This was an error, and the SetQueryDefaults activity no longer requires authentication.
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-131942 · Issue 574322
Orphaned CSS reference removed from DisplayReport harness
Resolved in Pega Version 8.2.8
An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.