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-125070 · Issue 186577
SOAPRequestEnvelope parameter added for custom Auth Activity
Resolved in Pega Version 7.1.8
In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".
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-125148 · Issue 178077
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-125148 · Issue 178317
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-125148 · Issue 192416
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.