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
PDF
The deployment instructions were somehow not updated with the recent submissions. Please refer to this readme for the latest instructions, including the change in the tenant definition that is required for version 3+
Will do so on the next release, thanks for the heads up
Documentation is still stating the tenant is something like: https/login/microsoftonline.com/. Could you update the documentation to show correct configuration.
bujard We are also getting same error. "Error executing the request". We are on latest version 22.2.
could you please tell us what exactly was the issue and what changes you made to fix this issue
Come across a couple of issues when trying to install the 3.1 application. into a 22.2 environment. (Locale en-GB)
1) the CDT for APP Mail Poller does not match the database definition. I had to manually edit the xsd definitions for the text columns to allow the datastore to be verified and published
2) The process model fails to import. . Import log displays the error: ValidationException: Process Model is not valid.
Hello Raymond,
Thanks for the reply, I was missing something on the upgrade and that was solved.
Thanks
That is often caused by not passing the proper tenant. Make sure that if you upgrade from an earlier version that you change the tenant from the full URL to just the id (see documentation for full details)
I'm getting an error in the logs "Authority Uri should not have empty path segments". I am upgrading from 2.4.2.
Hello Bujar,
Is there anything in the tomcat-stdOut.log that gives more details? The root cause can be various things, like a wrong tenant, wrong clientID / secret, connectivity issues or missing the database table / connection. The application logs usually provide a bit more insight.
If that does not provide more insight now, please add the following line to the appian_log4j.properties file: log4j.logger.com.appiancs.msgraphmail=DEBUG