Overview
Need to poll emails from your Exchange server? This smart service can be used in a poller process and extract the data from the Microsoft Exchange server. Messages are stored in the Appian Document System, as well as the attachments. Meta data is stored in a database table for further processing.
This plug-in provides an alternative to sending emails to an Appian process model when inbound email integration is requested. Instead of the email being forwarded to Appian, this plug-in reads the emails directly from the Exchange mailbox using the MS Graph API as described below:
Key Features & Functionality
All information how to deploy, configure and use the smart service is in the 'MS Graph Mail Poller.pdf' document in the downloaded zip. Extract the files in the ZIP and follow the instructions in the document.
Yes, there shouldn't be any other updates necessary. Let us know if that was not the case.
Please open a support case to request an earlier version.
Hi there,
We're trying to implement this plug-in for use in our self-managed system that is currently on 20.1. We're in the middle of upgrading to 22.4 but won't be live in production until after the end of the year. Per the tomcat logs in our nonprod, the pre-22.3 version of this plugin is not compatible with 20.1. Is there another version available for 20.1 while we complete our upgrade?
Thank you,
Tj
We are going to upgrade from 3.1.1 t0 4.0.1 . I was going through the deployment Instruction pdf and under Upgrade instruction found that it requires me to do all of the steps which i had done previously while upgrading to 3.1.1 , i.e. adding columns to APP POLLER and DOC tables, which are same as 3.1.1 and changing the tenant URL which we had done in 3.1.1 , which was to remove "login.microsoftononline..." from SCS (third party credential store). So could you confirm that if we upgrade to 4.0.1 , only thing for us is to upgrade the jar file and remap inputs and outputs?
Ah okay, I was not aware of that. We will upgrade the environment and the plug-in version at the same time. Thanks Raymond Braakhekke!
The version for 22.3 is on the cloud AppMarket, but you will only see it in your list when you are on 22.3 or above as it is not compatible with 22.2 and lower. If you would like to install the previous version of the plugin on a 22.2 or lower environment in the cloud, you would have to open a support case
Hello Raymond Braakhekke,
This plug-in is no longer listed in the Cloud AppMarket. Do you know when the latest version will be available on the cloud? We have to upgrade our cloud environments to 22.3 and are waiting on this plug-in version to become available.
We are concerned as this is a key requirement for our application. Thanks for your help!
Viren
This is not a poller specific thing, this is the general specification for the internet message id: it is globally unique. There is (and will not) be any additional checking in the plugin if there is already a message in the database with similar content, other than this unique key on insert. For testing purposes I usually remove this key, as I test with a specific subset of messages to cover a number of use cases.
In my case, whether or not to remove the unique key property, depends on what I was asking above.
Could you make sure that when the node returns the error "java.sql.SQLIntegrityConstraintViolationException: (conn=102596) Duplicate entry '<!&!YYYYYYYYYYY+...' for key 'UNIQUE_MESSAGE_ID'", it is because the message that the node is trying to insert in the database is identical (message body, subject, attachments etc...) to another one that already exists in the database?
If the answer is yes, then there is no need to remove the unique key property.
Regards,
Belén