<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Inbound Email Saved as Document</title><link>https://community.appian.com/discussions/f/general/12943/inbound-email-saved-as-document</link><description>We have a process model that is triggered by inbound emails, using the OOTB Receive Message Event. We are using the message properties to get the metadata about the email, and we are saving the subject, body, attachments, etc. 
 What I want to be able</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Inbound Email Saved as Document</title><link>https://community.appian.com/thread/136378?ContentTypeID=1</link><pubDate>Tue, 04 Jun 2024 16:07:47 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6c6f4346-284c-4bf1-88de-c92f32fb314d</guid><dc:creator>Lbeteta</dc:creator><description>&lt;p&gt;If you&amp;#39;re using the OOTB receive message event, this could be a potential solution. You can&amp;nbsp;use&amp;nbsp;the&amp;nbsp;&lt;a href="/b/appmarket/posts/create-read-email-files-utilities"&gt;Eml Utility&lt;/a&gt; plugin to convert the inbound email to an EML file. From there, you can have the user download and view the email. If the requirement is to view the email in Appian, you can convert the EML file into HTML or PDF using the&lt;a href="/b/appmarket/posts/eml-msg-conversion"&gt; EML&amp;nbsp;and MSG Conversion &lt;/a&gt;plugin.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;I personally haven&amp;#39;t used this approach, but in theory, it should keep the email formatting intact, which was the OP&amp;#39;s main concern.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Alternatively, I&amp;#39;ve worked on similar use cases using the &lt;a href="/b/appmarket/posts/mail-poller"&gt;Mail Poller&lt;/a&gt;&amp;nbsp;. We had a process on a timer that would kick off and process any new emails in a dedicated mailbox. The plugin processes the emails, creates an EML file, saves all attachments as Appian documents, and saves the email body as HTML along with other useful metadata. Hope this helps!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Inbound Email Saved as Document</title><link>https://community.appian.com/thread/136293?ContentTypeID=1</link><pubDate>Mon, 03 Jun 2024 13:53:56 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0db3cd80-50b9-46a2-b029-4b3c6298a9f7</guid><dc:creator>eyleenm420293</dc:creator><description>&lt;p&gt;Yes, this could be a solution if you don&amp;#39;t work with email threads, with email threads it becomes difficult to work this way and also putting it in a simple template. I thought that maybe there was some smart service or plugin that transforms an email into a file or something similar.&lt;br /&gt;Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Inbound Email Saved as Document</title><link>https://community.appian.com/thread/136285?ContentTypeID=1</link><pubDate>Mon, 03 Jun 2024 12:53:35 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6b586c33-7c9a-40f1-8f4d-75380e40a2ca</guid><dc:creator>karthikkanjerla</dc:creator><description>&lt;p&gt;Hi Ashvin,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;you can try using&amp;nbsp; this PDF tools plugin,&amp;nbsp;&amp;nbsp;&lt;a href="https://community.appian.com/b/appmarket/posts/pdf-tools"&gt;PDF Tools&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;create a template and use fill pdf and you can fill i the details as per the defined template from the pv! values which you get after you read the email subject, body etc.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Inbound Email Saved as Document</title><link>https://community.appian.com/thread/136284?ContentTypeID=1</link><pubDate>Mon, 03 Jun 2024 12:48:24 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:cb930d4b-2cdd-492e-9ff4-88f385bb3394</guid><dc:creator>Peter Lewis</dc:creator><description>&lt;p&gt;Yeah this might work if you store the data in the database and then display the text in the styled text editor field. I also think creating a PDF or HTML document like Ashvin originally suggested might work too. You&amp;#39;d probably need to create a template for those that would add the context about the subject, recipients, etc.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Inbound Email Saved as Document</title><link>https://community.appian.com/thread/136279?ContentTypeID=1</link><pubDate>Mon, 03 Jun 2024 11:32:07 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c52bf0de-0284-4db7-a9f6-0a3371a15f46</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;The new&amp;nbsp;a!styledTextEditorField() might be an option.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://docs.appian.com/suite/help/24.2/Styled_Text_Editor_Component.html"&gt;docs.appian.com/.../Styled_Text_Editor_Component.html&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Inbound Email Saved as Document</title><link>https://community.appian.com/thread/136277?ContentTypeID=1</link><pubDate>Mon, 03 Jun 2024 11:19:33 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:b2fb9b35-7aab-4110-966c-5e271e7a771e</guid><dc:creator>eyleenm420293</dc:creator><description>&lt;p&gt;Hi, any idea on it? &lt;a href="/members/peter.lewis"&gt;Peter Lewis&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Inbound Email Saved as Document</title><link>https://community.appian.com/thread/91581?ContentTypeID=1</link><pubDate>Fri, 25 Feb 2022 14:42:28 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:d889e80e-7d78-4599-8a3e-d2781ad35082</guid><dc:creator>bobt</dc:creator><description>&lt;p&gt;Hi Ashvin,&amp;nbsp; &amp;nbsp;I&amp;#39;m starting work on project with similar requirements and was wondering what solution you implemented to meet your requirements to store email message data and display in Appian user interfaces?&amp;nbsp; Did you leverage Tim&amp;#39;s suggestion or pursue other alternatives?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Inbound Email Saved as Document</title><link>https://community.appian.com/thread/58157?ContentTypeID=1</link><pubDate>Thu, 19 Jul 2018 21:37:57 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:08d521ea-eebc-4b38-8c36-394910353974</guid><dc:creator>Tim</dc:creator><description>I have worked on many projects where the html content of an email from msg!bodies is extracted and used to generate an html document. This method works particularly well in 18.2 where you can then combine the new web api and a!webcontent() functionality to display the formatted email on a dashboard or form.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>