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.
SR-A4056 · Issue 211550
Corrected validation error for Extract rule field length
Resolved in Pega Version 7.1.9
A validation error noting that the field length of the table was limited to 30 characters was occurring when trying to check in an Extract rule even if the field value had been shortened. While checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was recomputing the pagelist's table name instead of using the one provided by the user. The Rule-Utility-Function validateTreeProperties function has been modified to fix the issue.
SR-A1190 · Issue 205299
Corrected highlight alignment for Alt+ Key button selection
Resolved in Pega Version 7.1.9
If a button is clicked using hot keys (Alt + Key), a blue line is wrapped around the button to highlight its selection. However this blue line was expanded below the button and misaligned. This was caused by a margin-left of 0.3 mm on access key styles which has now been removed.
SR-A1604 · Issue 206062
Other Actions submit API updated
Resolved in Pega Version 7.1.9
When using the out-of-the-box Other Actions button, selecting 'Refresh' caused a blank page to display and resulted in an 'ERR_CONNECTION_RESET' script error. This happened when a form submit URL including all input parameters exceeded the max length expected. The API used for the submit function has been updated as of this release along with the Ajax engine call, and the problem is no longer seen.
SR-A1616 · Issue 205609
Fixed section refresh issue in Google Chrome
Resolved in Pega Version 7.1.9
When using the Google Chrome browser, a section that was included inside a repeating dynamic layout and configured to refresh based on the value of a radio button control which itself was included in another section and configured to post its value on change was refreshed as expected in dev portal but not in IAC. This was due to changes in the value list not populating properly in Google Chrome on IA, and the logic for parsing change tracker div has been modified to correct this.
SR-A1647 · Issue 205606
Removed duplicate special character encoding on FieldValue validation
Resolved in Pega Version 7.1.9
A recent change was made to the "Validate" activity of the Rule-Obj-FieldValue class to improve security by performing a filterRichText (intended to remove unsafe tags like script tag). However, this broke a reported use case where field values used as the source for the controls dropdown, checkbox, or radio buttons displayed the encoded values of quotes due to double encoding. To fix this, the filterRichText step has been removed from Rule-Obj-FieldValue!validate activity.