SR-124971 · Issue 188628
Button type filter added to Report Browser
Resolved in Pega Version 7.1.8
After navigating to the Report Browser and then back to another tab, clicking on any input field and clicking enter caused the columns filtering pop-up to appear even if the user was not on the Report Browser tab. This issue only occurred with the FireFox browser due to FireFox treating elements as the 'default action' of the form and using them as submits, causing a press of the enter key to fire off the onclick event for those buttons. In order to correct this, the type='button' attribute has been added to the filter
SR-125028 · Issue 187645
List View filter corrected
Resolved in Pega Version 7.1.8
When enable filtering is turned on in the display fields, the ListView filter tab failed to retrieve the record. This was traced to the Keycode 32(space bar) being conditionally added in pega_ui_listview, and has been corrected.
SR-125042 · Issue 193350
Corrected decimal field validation for special characters
Resolved in Pega Version 7.1.8
The '&' symbol was not being parsed correctly when entered into a decimal field. This was a tooltip issue with the ampersand character when the harness setting was set to full error text, and has been resolved.
SR-125044 · Issue 187842
Ampersand(&) handled as text and not parameter for data transforms
Resolved in Pega Version 7.1.8
When passing a parameter to a data transform, if the parameter value contained an ampersand ('&') or certain other non alphanumeric characters, an error was generated (visible in tracer) and the task failed. This was a case where an '&' character was not not handled as literal text, causing the RunActionWrapper to explicitly parse it and create params out of it. There was a local-change solution to directly reference a property value containing the required text value instead of passing it in via a parameter, but the system has been updated to encode ampersand(&) in the file pzpega_ui_events.
SR-125079 · Issue 187143
Fixed HTML title error in tooltip
Resolved in Pega Version 7.1.8
The tooltip of the error icon on a tab in a tab group was showing as "null" in the HTML title attribute. This has been resolved by adding the data-taberror attr to the td with id = 'tabcontainer', which is used to find the title of an error element in js.
SR-125091 · Issue 187602
Corrected display issue for treegrid with Microsoft Internet Explorer 9
Resolved in Pega Version 7.1.8
Using the Microsoft Internet Explorer 9 browser, the first column in the treegrid was not visible until there was a refresh in any section of the grid. This was due to mishandling of the container ID, and has been fixed.
SR-125143 · Issue 187274
Length limits for form URLs
Resolved in Pega Version 7.1.8
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 submit function has been modified to send only the required params as part of the URL, and not all hidden inputs.
SR-125196 · Issue 191599
Variable added for non-English fonts in RTE
Resolved in Pega Version 7.1.8
Previously, the dropdown for font styles in pxRichTextEditor control contained only English-language fonts and did not include fonts for other languages such as Japanese. To enhance the localization, the global variable 'window.customCKEditorFonts' has been added to override 'CKEDITOR.config.font_names' when desired.
SR-125254 · Issue 188703
Added Finish Assignment check for old harnesses
Resolved in Pega Version 7.1.8
After upgrade, a failing post flow action validation created the inability to correct the errors and resubmit using a pxButton which performed an out of the box "Finish Assignment." When trying to do so, a busy indicator was displayed and the application froze. This was caused by an incorrect legacy harness pointer for the Action section. A check for old harnesses has been added, and the submit API now sets the target of form submit for finish assignment to the parent window.
SR-125268 · Issue 188000
Added ownership check for DeleteModalHeader process
Resolved in Pega Version 7.1.8
When closing a modal dialog, the dropdown in the parent window became disabled and did not allow further selection. This was caused by the modal js throwing an error while attempting to remove an element that was not its child. To avoid this, the deleteModalHeader js API has bene modified to check the parent/child relationship before proceeding with the delete.