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)
Mike Cichy, We have a repeating issue where the email attachments are not getting extracted from original email. Sometimes the database entries point to AppianDocId but the document doesn't exist in KC. Any pointers or something we need to look for why this is happening? Any help in this matter is greatly appreciated.
I have not encountered this before but here a few questions:
Ramesh A Unfortunately, that is not much to go on. I inspected the code and the only thing that could be happening is that the document was deleted downstream by a person or process. Without more specific replication steps, I don't see a way forward in troubleshooting this.