INC-144948 · Issue 602273
Resolved JBoss memory leak
Resolved in Pega Version 8.5.2
JBoss logs indicated connection leaks. This has been resolved by limiting the scope of instance of ActionProvider, DataSyncRequestParser to a try-with-resources block which ensures that all resources are released.
INC-144970 · Issue 604952
Tags correctly displaying after Pega 8 Upgrade
Resolved in Pega Version 8.5.2
The context class for Tags was consistently picking up from the Access group but not consistently from the work class. This caused previously created tags in Pega 7 to not show up in Pega 8, and tags created through the Case Management->Social->Tag configuration were not showing up for user details. This was traced to several differences in the logic between the versions, and updates have been made to resolve this.
INC-146114 · Issue 604411
Create Survey routes case correctly
Resolved in Pega Version 8.5.2
The Create Survey utility was not routing the case to the user who initiated the case, but instead was routing it to the user who checked-in the case. This was traced to an error related to pxRequestor.pxUserIdentifier in the data transform pzpopulate survey params which is called when the survey utility is used, and has been corrected.
INC-146676 · Issue 601940
Field Service app localizations updated
Resolved in Pega Version 8.5.2
Localization has been added to the 'getDirections' alert and other popup alerts in the Field Service app.
INC-148727 · Issue 603752
Activity updated for Mobile attachment access
Resolved in Pega Version 8.5.2
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
INC-131384 · Issue 584856
Documentation updated for troubleshooting inline images for email
Resolved in Pega Version 8.5.2
Inline images were not showing by default when sending emails. To assist in this, the troubleshooting information for email has been updated with the following information: Correct configuration for display of inline images via Email bot is one that is shipped standard. To support Rich text in email display via Email bots, Email body must be stored 'As HTML attachment' (the setting on auto generated Service Email rule). In addition, no other setting on listener must be changed especially 'Embed inline images'(should remain unchecked) on Email listener rule. Combination of these 2 settings causes Email bot to save - 1. Email body as attachment 2. All inline images as attachment At runtime UI display, these 2 are recombined to display proper email. This is done in order to increase performance because images are lazily loaded.
SR-D92590 · Issue 553059
PostgreSQL information updated in Platform Support Guide
Resolved in Pega Version 8.5.2
The Platform Support Guide has been updated to reflect the following:Postgresql-42.2.14.jar supports PostgreSQL 8.2 or newer, and requires Java 6 or newer (Pega only supports Java 8 and 11); this driver also contains support for SSL and the javax.sql package. Prior versions of this .jar file have known problems. Do not use these versions: • 42.2.11 – creates an exception which stops Pega Platform startup • 42.2.12 and 42.2.13 – known vulnerability issues (CVEs) reported