INC-218361 · Issue 737014
AttachmentEmbededInHtml flag works with Microsoft Graph
Resolved in Pega Version 8.8
When an email was received with inline attachments such as images in the signature or an attached file like a Word or Excel document, the attachments were saved into Data-WorkAttach-File but the flag "pyAttachmentEmbededInHtml" used to differentiate whether these attachments were inline attachments or not was not being set consistently when the email was sent from an external domain. This was was missed use case related to Microsoft Graph where pyAttachContentDisposition was not being set to inline for inline images, and has been resolved by updating pzCreateInteractionReply.
INC-212251 · Issue 720198
Editable data page properly refreshes after interaction
Resolved in Pega Version 8.8
A data page using editable mode was adhering to the "Reload once per interaction" option used for readonly mode. This led to issues such as tables not refreshing after sorting or applying filters. To resolve this, refreshReloadInteraction has been updated to false when mode is not readonly.
INC-220076 · Issue 720198
Editable data page properly refreshes after interaction
Resolved in Pega Version 8.8
A data page using editable mode was adhering to the "Reload once per interaction" option used for readonly mode. This led to issues such as tables not refreshing after sorting or applying filters. To resolve this, refreshReloadInteraction has been updated to false when mode is not readonly.
INC-220789 · Issue 720198
Editable data page properly refreshes after interaction
Resolved in Pega Version 8.8
A data page using editable mode was adhering to the "Reload once per interaction" option used for readonly mode. This led to issues such as tables not refreshing after sorting or applying filters. To resolve this, refreshReloadInteraction has been updated to false when mode is not readonly.
INC-178831 · Issue 680984
Ensured correct context for multi-select
Resolved in Pega Version 8.8
When using multi-select controls, there was an intermittent issue with selecting values using a mouse click. Using the tab key worked as expected. This was traced to the focus being event triggered multiple times so pega.ctx.dom returned undefined values in the second call.This has been resolved by focusing the target element before creation of capsule to ensure the context remains the same.
SR-A92126 · Issue 261816
Bulk Action transfers all selected records
Resolved in Pega Version 7.2.2
Not all of the selected cases were being transferred when using the Bulk Actions functionality to transfer. This was due to the pySelected values to not being updated in the clipboard. To resolve this, a Refresh other section has been added to Select Action in pzBulkProcessingActionSection to update the value when clicked.
SR-A88035 · Issue 257024
Localization added for 'Close All' functions for multiple tab views
Resolved in Pega Version 7.2.2
Localization has been added to the 'Close All' menu item and tooltip that appear when multiple tabs are present, using the new field value pyMessageLabel.
INC-147873 · Issue 610864
Custom header character encoding for Subject added
Resolved in Pega Version 8.4.4
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
INC-208424 · Issue 707613
Custom header character encoding for Subject added
Resolved in Pega Version 8.8
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
INC-199469 · Issue 707514
PDF margins made available as parameters
Resolved in Pega Version 8.8
After update, margins were different in exported PDFs. This was due to upgraded jar files: PD4ML v3 used setPageInsets(new Insets(top, left, bottom, right)) , but the v4 jar uses setPageMargins(new PageMargins(left, top, right, bottom)) . Because the order of values (20, 10, 10, 10) were not changed this produced a different result. To resolve this, PD4ML margins are now available to be set as parameters: Param.pyMarginLeft, default value 20 Param.pyMarginTop, default value 10 Param.pyMarginRight, default value 10 Param.pyMarginBottom, default value 10 When standard activities like HTMLToPDF / pyViewAsPDF / pyAttachAsPDF are used, add a Property-Set step before calling the activity to add the necessary margin parameters. When CreatePDF smart shape is used, set the parameters via the connector of the CreatePDF.