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-163292 · Issue 635837
Portlet service deprecated
Resolved in Pega Version 8.4.6
Portlet authentication services have been removed from the standard installation package.
INC-156674 · Issue 660956
Handling added for reactivating combined Passivation and AccessGroup timeout
Resolved in Pega Version 8.4.6
Refreshing a passivated browser window in Dev Studio for an operator with a combined access group and passivation timeout was resulting in a blank screen after re-authenticating. InvalidParameterException and InvalidReferenceException messages were logged. Research showed this was caused by a missing pxPortal property on the pxThread page along with missing Application and Accessgroup pages. While refreshing the browser along with the top URL, there will be few requests with tab threads calling activities such as deletedocumentpg and SetProcessWindowName because there was an unload. Because these requests reached the server before re-authentication, the threads proceeded to the activation flow, causing properties such as pxPortal, Application, and Accessgroup pages to be removed from the thread page and requestor page according to the condition that the requestor was not yet authenticated. To resolve this, the logic in session.internal.authorization.context.BasicApplicationContextImmutableImpl#applyApplicationProperties has been updated to skip removing application page properties from the thread page in this combined Passivation and AccessGroup timeout scenario.
INC-165722 · Issue 636327
Stack trace logging enhanced for engine startup issues
Resolved in Pega Version 8.4.6
Enhanced stack trace logging has been added to capture additional information when the application is unable to start and no PegaRULES logs are generated.
INC-170458 · Issue 667374
Handling updated for queue processor locks
Resolved in Pega Version 8.4.6
The Final activity mentioned in the processing epilog of the Service File rule was not being consistently called from File Listener, causing some of the cases to become stuck and not continue to the next stage. Investigation showed that if the lock was held by the queue processor requestor, the system was unable to obtain the lock but still proceeded to update the LogServiceFile page and persist it. This resulted in overwriting changes made on the LogServiceFile page by the requestor, resetting the completed-batches-count set back to 0. To resolve this, RuleServiceFile -> updateLSFBatchCounts() will call the overloaded lockAndLoad() method in LogServiceFile that accepts a parameter called lockAttempts. This will attempt to obtain a lock for a given number of times before throwing an exception.
INC-174612 · Issue 659249
Queue Processor threads explicitly cleared before new interaction
Resolved in Pega Version 8.4.6
Queue Processor was not clearing already evaluated freshness caches before running an activity, potentially causing a stale data page to be processed. This has been resolved by explicitly clearing the thread on a new interaction by invoking ((IPRThread) thread).clearOnNewInteraction.
INC-177773 · Issue 665339
Tracer protections updated
Resolved in Pega Version 8.4.6
Cross-site scripting protections have been updated for Tracer.