INC-185045 · Issue 672418
Performance improvements for action check-in
Resolved in Pega Version 8.6.2
The process of 'Saving As' an action to a higher ruleset, Saving, and then running Check-in was taking an excessive amount of time. This was traced to redundant page copy activities and performance has been improved by updating the implementation.
INC-186889 · Issue 674015
Unused DSS compiledExpressions now defaults to false
Resolved in Pega Version 8.6.2
After updating from Pega 8.2 to Pega 8.5, executing a test campaign failed with an error in logs. This occurred when running Distribution tests with "Include funnel analysis reports" checked, and was traced to the DSS setting "decision/strategy/ssaVM/compiledExpressions". As this was previously used to toggle a feature which is no longer in use, the default setting for this DSS has now been changed to false to resolve this issue.
INC-188389 · Issue 672761
ComponentName fallback added for toggling page context
Resolved in Pega Version 8.6.2
Whenever the External Strategy configuration was changed from "Another Page" to "Current Page", pyComponentName property was not being created. This was a missed use case for toggling page context for external substrategies in the user interface of the strategy designer, and has been resolved by setting pyComponentName to its default if reset when switching context.
INC-188419 · Issue 671500
DSS added to configure usage of Topup
Resolved in Pega Version 8.6.2
During NBAD-generated strategy execution, each interaction history summary is queried twice to check data relevancy. This update adds configuration options to disable topup in aggregate datasets. Topup can be disabled with the following configuration items:- Set prconfig "ih/aggregates/last_customer_update_method" to NONE - Set DSS "cep/aggregates_dataset/partition_proc_cache_time" to -1
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.