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)
Hello Mike,
Thank you for the update.
Yes we have TLS1.2 connection set up.
Regards,
Sreeraj
Yes, the version that was just published (1.1.6) is compatible with the latest update to Java and 21.3.
Please be mindful that the plugin will no longer work with TLS 1.0 or 1.1, so make sure your mail servers have the right support.
Hello,
The new version of the service which is compatible with 21.3 is available for user?
Any update on the availability of above mentioned issue fixed version?
Thanks for the update. Will wait for the fix to be available.
We just found about this yesterday - it is actually the Java upgrade that likely coincided with your Appian upgrade that breaks the plugin. We have identified a fix and should have it available by the end of the week.
This plugin is giving an error "No appropriate protocol (Protocol is disabled or cipher suites are inappropriate) " .
The plugin was working fine until now.
But this behavior is encountered post the 21.3 upgrade(Not sure if this is the cause and also there is no changes to the shared mailbox). Any help or suggestions?
Ramesh, per our offline conversation, this behavior is now addressed and you have successfully tested the resolution.
The plugin gives you the basic structure of the message. What you do with it afterwards, how you process it, and how you handle marking it as processed is up to you. You could add a column to the table or create a new one with a foreign key pointing to the message table. Or you could delete the message from the table if you so choose.