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
We are utilising a MariaDB Connected System to define our data source, which is in a separate schema on the Appian Cloud DB (i.e - not the default "Appian" schema).Is there any way to supply the Connected System data source as an input to this plugin's smart service, instead of a JNDI reference? Or will we still be required to add our data source in the Admin Console for this to work?Thanks!
This is because the OAuth client credential grant needs this to work. You can limit the mailboxes the poller will have access to though. More information: learn.microsoft.com/.../auth-limit-mailbox-access
Hi Team,
We have query regarding - "Select Grant Admin Consent for Appian".
Client is asking why Admin Consent is needed?
Thanks, sir. A case has been opened.
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!