INC-153877 · Issue 612369
Enhanced socket timeout logging
Resolved in Pega Version 8.6
In order to assist with diagnosing issues with socket timeouts such as a Data Flow Daily Run failing, logging to print the SocketTimeout value has been added when case info is enabled.
INC-153895 · Issue 628174
Correspondence rule finds updated content
Resolved in Pega Version 8.6
Activity Method Property-Set-Stream retrieved the older content of Correspondence when triggered via Queue processor. Restarting the queue processor resolved the issue until the next correspondence update, and then the cycle repeated. This has been resolved by adding an explicit thread cleanup to remove cached rules.
INC-154026 · Issue 630869
Resolved exception from expanding deserialized Data Page
Resolved in Pega Version 8.6
When using a data page backed by a report definition where the data page data type was Rule- and the virtual page data type was Rule-Obj-Property, serializing and deserializing the data page and then expanding the deserialized data page generated the exception "the reference .pzInsKey is not valid. Reason: .pzInsKey is mapped to class Rule-Obj-Property, which is not the primary class of the list: Rule-; must specify a group name in mapping". The issue occurred only if "Run on Data Page" on the data page was checked and "Report on descendant class instances" on the report definition was unchecked, and has been resolved by updating the runLoadActivity() of DeclarativePageDirectoryImpl to skip setting pyObjClass for the report definition if it already present, i.e. if already set by the loader activity.
INC-154062 · Issue 614021
Optimizing helper class enhanced to handle external databases
Resolved in Pega Version 8.6
Running a BIX extract that included a manifest for a target database was resulting in a null pointer exception for the manifest extraction. Attempting to generate the DDL for the manifest table also failed. This was traced to an issue with the helper class using a hardcoded default database for forming the queries, causing it to ignore the database config/DADN/prconfig for the Oracle database and form a query using the PegaRules' database credentials. This only occurred when trying to do external database operations on a different database platform; Oracle PegaRules worked as expected with an Oracle external database and Postgres Pegarules worked with a Postgres external database, but mixing Postgres PegaRules and an Oracle external database would result in the null pointer exception. To resolve this, the helper class has been enhanced to work with external databases by passing the database name as a parameter so it will properly calculate the query based on the type of target. An error in the name of the class has also been corrected, and is now available as PerformanceHelper rather than the previous "PerformaneHelper".
INC-154434 · Issue 621568
Additional logging added for exceptions related to agent restart
Resolved in Pega Version 8.6
One Legacy agent, AgentBulkProcessing, was failing to restart following a database connection issue even though the 'always retry' flag was enabled. Research indicated that an exception was occurring during the evaluation of whether the agent should be stopped or rescheduled with a delay, but that exception was suppressed by an additional exception from a database connection error. This is standard Java behavior related to exceptions thrown from a finally blocks. To resolve this, a catch to improve troubleshooting has been added which will log any exception that may be suppressed by an exception thrown in finally block.
INC-154605 · Issue 615660
Date field correctly extracted for IMAP inbound email
Resolved in Pega Version 8.6
After upgrade, email-sourced cases were not being created correctly. Tracer showed the date field was blank, causing an error which was traced to the getReceivedDate being returned as null for the JavaMail AP even though the IMAP protocol was being used. This was an unintended side effect of work done to handle a throttling exception in the IMAP inbound email flow, and has been resolved by updating the system so that if the getReceivedDate is null, the date will be extracted from the mail header while processing dates in EmailMessageInfo class.
INC-154884 · Issue 614731
Dataflow statistics will fetch 5000 results
Resolved in Pega Version 8.6
In order to accommodate large Dataflow runs, the configuration in the report definition has been increased from pulling the first 50 records of dataflows to pulling 5000 rows, and the pagination has been removed.
INC-154889 · Issue 617189
Corrected export of zero value as '0E-9'
Resolved in Pega Version 8.6
File Data Set was exporting properties such as pxPriority and pyPropensity as '0E-9' if the value was 0.00000 . This has been corrected.
INC-155294 · Issue 626662
Enhancement added for attachment size handling with Kafka
Resolved in Pega Version 8.6
Attempting to send an email attachment larger than 2 MB resulted in the error "Caused by: org.apache.kafka.common.errors.RecordTooLargeException: The message is 8101592 bytes when serialized which is larger than the maximum request size you have configured with the max.request.size configuration." This has been resolved by updating the Stream SPI size to 2.0.5-14 to support custom producer configurations. The settings can be passed as environment parameters, for example 'Dstream.producer.max.request.size=500990'.
INC-155573 · Issue 617517
Email Listener updated to handle double quotes
Resolved in Pega Version 8.6
The From field in Requestdata was blank for emails that had a FROM address that contained double quotes, causing them to not be read by the email listener. This has been resolved by modifying the regex pattern to accept double quotes, square brackets, and any ASCII characters between quotes.