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-119646 · Issue 563696
RemovePrivateBlockedAndWithdrawnRAQs updated to avoid exception
Resolved in Pega Version 8.4.2
If the method removePrivateBlockedAndWithdrawnRAQs() (present on the AgentRuleUtils.java class) had both the "ignore personal rulesets containing checked out files" and "ignore "Blocked or Withdrawn agent" conditions set, raqsItr.remove(); ran twice and resulted in a java.lang.IllegalStateException. This could lead to undesired outcomes such as agents not showing up properly. To correct this, the code has been refactored to avoid running raqsItr.remove(); more than the necessary number of times.
INC-125193 · Issue 561461
Processed in last hour generated correctly
Resolved in Pega Version 8.4.2
After upgrade, the 'Processed in last hour' for pyFTSIncrementalIndexer (or any other queue processor) did not show the totals processed. This was traced to an error in a declare expression rule, and has been corrected.
INC-128654 · Issue 567410
Queue processor handling updated
Resolved in Pega Version 8.4.2
After upgrade, the queue processors were not processing all the items in the queue, however the value under the 'number of items processed in the last hour' in the Admin studio showed the value was equal to the total number of items in the queue. This was traced to the an incorrect offset kept by the queue processor in the data table (Data-QueueProcessor-Run-Partition). Because the incoming messages from Kafka have a lower offset than the one kept by the queue processor, messages were treated as duplicates and not processed. This has been resolved by adding a partitions-validation mechanism on QP startup. To assist in proper handling, any messages identified as potentially already processed will be moved to the broken messages queue.
SR-D85839 · Issue 550939
Support added for custom Kafka connection properties
Resolved in Pega Version 8.4.2
An enhancement has been added to allow specifying custom Kafka connection properties in the Data-Admin-Kafka data instance to allow connections to external Kafka through the common client configs, ssl configs, and sasl configs.
INC-100288 · Issue 555466
Declaratives disabled during startup
Resolved in Pega Version 8.4.2
Declaratives firing before the engine is fully up can lead to null pointer errors. In order to avoid this condition, declaratives will be disabled during startup so that unnecessary operations can be avoided and system can be started faster.
INC-119678 · Issue 564202
Improved timing for node tracing termination
Resolved in Pega Version 8.4.2
The tracer stopped tracing after tracing a certain number of events. This was due to communication timing issues for tracer events from one node to another node in a multi-node cluster environment, caused by the Tracer Client using the pzMaxEvent property which limited the maximum number of events fetched at a time to 200. Any leftover Events should have been fetched in the next request, but when the consuming node's service ended after the 200 events, the system removed the service requester entry from the distributed Map and disabled remote node tracing as part of cleanup of the service execution. To resolve this, an update has been made so the node tracing will not be terminated until the service execution ends and there are no more events to process.