Overview
This version is for Appian 22.3 and above. Cloud customers on a lower version of Appian that want to install this plugin should open a support case. Self-managed customers can find the latest jar for Appian 22.2 and lower version by downloading from the app market.
Enhancement to the plug-in to enable the selection of whether or not to include the email attachments as part of the EML document. Previously, the plug-in would create an EML document with the attachments stripped out. Our client needs to preserve the original e-mail as it was sent (for auditing purposes), so the EML must include the attachments as part of it. This update extends the functionality to allow the user to select whether they want an EML with the attachments removed (original functionality), an EML with attachments included, or both (2 EMLS of original email - one without the attachments included and one with the attachments included). Any e-mail attachments will continue to be saved separately.
Key Features & Functionality
Takes all unread email from a mailbox and adds entries directly to a database table.The original email is saved as an EML based on three attachment type options
Each email attachment is saved as its own document. The database tables store the Appian document ids, email recipients, subject and body (text and HTML)
Hi Mike,
We have an issue with attachments that are extracted from the original email. Attachment names are completely changed when writing to KC.Please see below examples and we believe it could be with special characters in attachment name.
Original Attachment Name: Don’s Speed_Adj. 1st Report_1100.pdf
After extracting the attachment from original email, the current name in KC=_utf-8_B_RG9u4oCZcyBNY05lZXNlIEV4cHJlc3MsIExMQ19BZGouIDNyZCBSZXBvcnRf_= =_utf-8_Q_10997127.pdf?=
If there are no characters like ( ’, or any special character) then the name is perfectly fine.
The issue is more around the extension when processing documents as its an invalid extension(.pdf?= ). We can do a workaround and replace it but wanted to check if this can be fixed or addressed from plugin side? Please let me know your thoughts. Mike Cichy
Ramesh, per our offline conversation, this behavior is now addressed and you have successfully tested the resolution.