MSGraph Email Poller

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:

  • Reads the mailbox using the MS Graph API
  • Convert the email to an EML file stored as an Appian document; Item attachments (calendar invites, messages) are kept in the eml file, File attachments removed from it and stored separately in the document management system.
  • Store all email file attachments as separate Appian documents
  • Store all email metadata (subject, author, recipients, etc...) into a set of tables in the database

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.

Anonymous
Parents
  • Hi,


    We are doing a database migration from Appian, to a database located in AWS of Aurora PostgreSQL type.
    We have created the tables in the postgresql database and also performed the data migration, but we have had 2 problems when configuring the plugin:

    - The first one is: is it mandatory that the plugin node connection in the Jndi Name field is configured in the Appian Management Console, can't a connected system be used?

    - After creating the connection in Appian Admin Console and pointing to our postgresql database in AWS, we have executed the node and it returned the following error: "Unsupported database dor processing email: PostgreSQL"

    {errorOcurred=true, errorMessage=Unsupported database for processing email: PostgreSQL, timeLimit=false, mailCount=0, errorCount=0}

    Does this mean that the plugin does not support postgreSQL databases? Is there any extra configuration to do? Why does this problem occur?

    The only difference in the configuration with the Appian database was the Jndi Name, the rest is the same and with the Appian database, it worked without any problem.

    Thank you very much and best regards

Comment
  • Hi,


    We are doing a database migration from Appian, to a database located in AWS of Aurora PostgreSQL type.
    We have created the tables in the postgresql database and also performed the data migration, but we have had 2 problems when configuring the plugin:

    - The first one is: is it mandatory that the plugin node connection in the Jndi Name field is configured in the Appian Management Console, can't a connected system be used?

    - After creating the connection in Appian Admin Console and pointing to our postgresql database in AWS, we have executed the node and it returned the following error: "Unsupported database dor processing email: PostgreSQL"

    {errorOcurred=true, errorMessage=Unsupported database for processing email: PostgreSQL, timeLimit=false, mailCount=0, errorCount=0}

    Does this mean that the plugin does not support postgreSQL databases? Is there any extra configuration to do? Why does this problem occur?

    The only difference in the configuration with the Appian database was the Jndi Name, the rest is the same and with the Appian database, it worked without any problem.

    Thank you very much and best regards

Children