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,
Our team has taken poller plugin version 1.1.7 and customised the plug-in code and also made the following changes -
log4j Version was updated to 2.17.1Also, the code was refactored including package names. (com.<companyname>.integration.mail)
We are not aware how or where to configure log4j properties in Appian to match the log4j version. Can you please advise?
We are using Appian 21.4 currently.
Seems like the changes did not come through.
The log4j lib is not included with the jar, so the plugin use the latest logging library in the base product. I'm not sure what you mean by configuring log4j properties, why do you need to do that?
Do you want to submit a new version to the AppMarket here or are you creating a completely new plugin? If the latter, make sure the plugin key in appian-plugin.xml is also updated. If you want to incorporate your changes into this plugin, please send me the source code for review, but for starters the package names will need to be reverted.