SR-D41616 · Issue 509808
Corrected Cassandra startup error related to client authentication
Resolved in Pega Version 8.3.1
During provisioning, Cassandra nodes in PegaDDSTier failed to join the cluster and the error "Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered during startup: Invalid yaml. Those properties [truststore_password, truststore] are not valid" was generated. Investigation showed that the recent addition of support for client authentication using the settings "dnode/cassandra_client_encryption/truststore" and "dnode/cassandra_client_encryption/truststore_password" resulted in nulls being set cassandra.yaml if the new parameters were not given values. To resolve this, truststore and truststore_password will not be added to cassandra.yaml when they are not set in prconfig or system settings.
INC-202878 · Issue 713790
Handling updated for social messaging items with very large embedded images
Resolved in Pega Version 8.7.2
Job scheduler was running out of memory while handling large/multiple files, causing nodes to crash while handling Social Messaging items. Inline images were also not being sent in the ACK email. Investigation traced this to a custom job scheduler and activity used to create PDFs from email communication and send the PDFs to a third-party system. This used the standard Email Triage/PegaSocial functionality for the emails, which were stored as instances of PegaSocial-Message. The custom Job scheduler and activity then leveraged the Data Page D_pxEmailPosts to retrieve the emails in order to harvest the text from the emails. The issue occurred when a number of the emails had multiple or large embedded images in them, meaning the PegaSocial-Message instances are very large. This resulted in the node running out of memory and crashing. To resolve this, code has been added to support inline images in ACK email and the complete message from Pulse will be used instead of the original message as the email body for the ACK email.
INC-211417 · Issue 711610
Updated URL construction for inline images for better performance
Resolved in Pega Version 8.7.2
System slowness was seen, and inline images were not getting displayed when the case was opened. This has been resolved by modifying pyExtractHtmlFromAttachment to ensure the image source URL is built in a consistent way whether or not there is a cache to call from.
INC-212549 · Issue 706073
HTML attachments conditionally shown in email listener cases
Resolved in Pega Version 8.7.2
When Rich text/html (non-plain text) emails were ingested in email, the original mail was not getting added to the case. Investigation showed that the pzCreateTriageWork activity had an explicit delete step to remove any attachment that started with 'email-content'. Since the HTML attachment name starts with 'email-content', it was deleted in above activity. This has been resolved by adding a when rule named 'pyLinkEmailTriageContentHTML' which will conditionally show email-content.html.
INC-212966 · Issue 713955
Support added for email attachments stored in repositories
Resolved in Pega Version 8.7.2
Attachments sent through email were received as corrupted. To resolve this, support has been added for retrieving content attachment file content from external repositories using data page D_pzGetExtStorageContent[ContentLocation:.pyContentLocation,RepositoryName:.pyStoredInRepository].pyFileSource
INC-214294 · Issue 710827
PopulateEmailClientWorkFilter correctly resolves field value
Resolved in Pega Version 8.7.2
The first item in the Email manager queue selection dropdown was 'DefaultWorklist', instead of 'Default worklist' or other formatted text. Investigation showed the New Page was not created for the temp results in pzPopulateEmailClientWorkFilter Activity, preventing it from resolving the customized/available field values, and this has been resolved.
INC-179727 · Issue 704544
Modified batch requestor handling to ensure cleanup
Resolved in Pega Version 8.7.2
A large buildup of batch requestors was seen, and restarting the node did not clear it. Investigation showed that in the case of one class reading a DSS value, a Pega requestor was being created when it was unable to retrieve any Pega context, and this requestor was not cleaned up afterwards. To resolve this, an update has been made to the way the requestor and Pega context is being created along with ensuring it will be cleaned up properly after use.
INC-192826 · Issue 685795
PMML updated for nested 'if'
Resolved in Pega Version 8.7.2
Running a model on the openscoring API and the Pega PMML model gave different results. This has been resolved by updating the handling for nested 'if' in PMML.
INC-206109 · Issue 706237
Delayed Learning works correctly with Volume Constraints
Resolved in Pega Version 8.7.2
When running an outbound campaign using NBA Designers predictions and delayed learning in conjunction with volume constraints, the adaptive models ended up with incorrect feedback if the prediction had an Alternative label configured with a defined waiting window. This has been resolved with the addition of a new flag 'isVolumeConstraintEnabled' during dataflow creation which will check for volume constraint, and a filter in HandleResponses for that flag.
INC-207357 · Issue 703349
Decision Management book updated for additional NLP troubleshooting
Resolved in Pega Version 8.7.2
Troubleshooting articles have been added to the Decision Management book which address the most common issues encountered when working with the NLP capability of Pega Platform, including topic and entity detection and email parser. These tips can assist with issues such as a node running out of memory due to having a large number of custom Ruta scripts that use REGEX pattern matching.