SR-132919 · Issue 201479
REST querystring not forced to lower case
Resolved in Pega Version 7.1.8
A Rule-Service-REST.validate activity which forced the query string to lowercase was leading to REST services are not receiving the input values in case of capital or camelCase query strings. To resolve this, the code that fetches querystring name for REST will not convert it to lower case.
SR-128332 · Issue 199072
Added detection for WSDL import failure
Resolved in Pega Version 7.1.8
Issues were encountered while importing WSDL in the ML6 environment while SoapUI was successful using the same SOAP service. This error happened when the WSDLParser.parse(Reader) was trying to read a closed java.io.Reader instance and silently generating an exception. Error handling has been added to report the failure and give an informative message.
SR-129312 · Issue 198553
Corrected HTML display of characters in reply emails
Resolved in Pega Version 7.1.8
HTML characters were appear in the email body and subject for outbound reply messages. For example, if subject is test, the reply email would display the subject as RE: test<%gt; An HTML reply to an HTML email did not contain these entities/artifacts. Reply emails can now be configured to use HTML format, and the 'HTML' option has been added to the Message Type drop-down on the Response tab of Service Email rule.
SR-131612 · Issue 200253
Handling added for accent characters in DataTable editing
Resolved in Pega Version 7.1.8
When a DataTable had a key value with an accented character like "é", clicking on the "Open this item" icon to edit the row displayed a blank page in the editor. This was caused by the escape method of native JavaScript being deprecated, and the system has been updated to use encodeURIComponent method instead.
INC-121480 · Issue 595824
EnableRedirects property added for REST connections
Resolved in Pega Version 8.5.3
When implementing a connector with the header �Location� which contains a redirect URI, a 303 response code was expected. Instead, a 400 or 404 error was generated. It was not possible for developers to process the code per their logic in Activity as Connect REST processed 303 responses automatically - i.e. there was no intercept points to implement the suggested approach. To resolve this, the new property "Rule-Connect-REST.pyEnableRedirects" has been added along with a checkbox for the property in "Rule-Connect-REST.pyService" in "Connection" section. Logic has been added in RESTConnector.java to take value of this property and set it on the HTTPClient being used, and a method has been added to HTTPClient interface and ComponentsHTTPClient to use the new value being passed. The default behavior is the same for the REST Connector, but a client can uncheck a checkbox on the REST Connector ruleform to stop the HTTP client from automatically following any compatible 3xx responses.
INC-135065 · Issue 598717
Added Database query optimization and cache invalidation logging
Resolved in Pega Version 8.5.3
Web nodes were going down during deployment due to failed health checks. This was traced to queries firing even when there was no rule change, and was due to unnecessary cache invalidations. An update has been made which will optimize and analyze declarative database queries and capture diagnostic details on any invalidation of the declarative reference information cache.
INC-143668 · Issue 617485
Performance improvements for Attachment Migration Utility
Resolved in Pega Version 8.5.3
The Attachment Migration Utility was showing a zero count for attachments in the Pega Database. This was traced to the underlying report definition that retrieves data for the Attachment Migration Utility timing out, and has been resolved by updating the activities to improve performance for applications having a large number of attachments without customization.
INC-145756 · Issue 619294
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.5.3
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
INC-146610 · Issue 610483
MimeTypeHandler added for cloud downloads on mobile
Resolved in Pega Version 8.5.3
When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the Google Chrome browser on an android device, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so Google Chrome on mobile was not able to identify the file type. This was a missed use-case for returnFileForDownload(), and has been resolved by setting the system to use MimeTypeHandler for getting the content type.
INC-147669 · Issue 614884
Enhanced logging added to REDUX query references
Resolved in Pega Version 8.5.3
Diagnostic logging has been added to REDUX query references which will capture information about exceptions that cause the system to fallback to generating legacy references.