Information
  • Author: Appian Corporation
  • Type: Plug-in (Function & Smart Service)
  • Support: This plug-in or utility is not supported by the author. The content is free to use with a licensed product, but it is made available as-is and Community supported.
  • Industry: All Industries
  • Compatible Version(s): 22.3+
  • First Released:
  • Last Updated:
  • Cost: Free
Resources
Share
Home » AppMarket » Create & Read Email Files Utilities

Create & Read Email Files Utilities

Use Case Details

This Plug-in contains Functions and Smart Services that allow users to create and read email files containing all e-mail attributes, i.e. to, cc, bcc, from, subject, body, content type, and attachments. The generated file can be read by any email client that supports EML files, such as Outlook Express and Windows Live Mail. The Plug-in and a help guide are provided with this listing.

This version is for Appian 22.3 and above. Cloud customers on a lower version of Appian that want to install this plugin should open a support case. Self-managed customers can find the latest jar for Appian 22.2 and lower version by downloading from the app market.

Features & Functionality

Smart Services:

  • Creating EML File: Create Eml File
  • Reading EML File: Read Eml File

Features:

  • Creates Email files/documents that can be read on all email clients supporting eml files.
  • Reads all email files to extract all email-related attributes such as to, cc, bcc, subject, body, attachments, content type.
Anonymous
  • v2.0.5 Release Notes
    • Updated bodyTypes as they were not handling correctly while creating the EML

  • in reply to juancarlosl0002

    Hi ,
    We haven't implemented any workaround for this issue as it cannot be fixed from Designer side. The author of this component has fixed this issue and it will be listed soon.

  • in reply to dineshd

    We upgraded to 23.1 yesterday and had to update this plugin, and since then, we have the same issue as you. What workaround did you implement until the fix is released?

  • Hi Team,

    We are creating an EML file with HTML text as body and the created eml file is showing the body with HTML tags instead of formatted text.

    We have found a fix for this issue: 

    We can set the Content-type header of bodyPart to text/html to display the body content as HTML formatted text instead of text with HTML tags.

    bodyPart.addHeader("Content-Type", "text/html");

    It would be convenient to have Content type of body as a separate AC input/ Parameter for setting the same in the created EML file. 

  • Good morning team,

    We recently upgraded our Appian environment to 22.4 and we are seeing errors while our processes are triggering 'Create Eml File'.

    Please see the logs below:

    2023-03-20 13:07:08,170 [ThreadPoolTaskExecutor-3154] ERROR com.appiancorp.process.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [[WorkId: 565, EngineId: execution02, Request: UnattendedJavaActivityRequest:73036 as AppianAdmin by AppianAdmin, ProcessId: 3042421, ProcessModelId: 48, Response: null]] - Exception: 
    javax.resource.spi.work.WorkCompletedException: java.lang.NoClassDefFoundError: javax/mail/Address
        at org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter.run(SimpleTaskWorkManager.java:244)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
    Caused by: java.lang.NoClassDefFoundError: javax/mail/Address
        at com.appcino.plugin.emlutility.smartservice.CreateEmlFile.run(CreateEmlFile.java:45)
        at com.appiancorp.process.runtime.framework.DefaultActivityExecutor$1.lambda$call$0(DefaultActivityExecutor.java:136)
        at com.appiancorp.plugins.PluginUsageLogger.runWithPluginInformation(PluginUsageLogger.java:52)
        at com.appiancorp.process.runtime.framework.DefaultActivityExecutor$1.call(DefaultActivityExecutor.java:136)
        at com.appiancorp.process.runtime.framework.DefaultActivityExecutor$1.call(DefaultActivityExecutor.java:130)
        at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:27)
        at com.appiancorp.process.runtime.framework.DefaultActivityExecutor.execute(DefaultActivityExecutor.java:130)
        at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
        at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse(UnattendedJavaActivityRequestResponseCreator.java:22)
        at com.appiancorp.process.engine.UnattendedJavaActivityRequest.getJavaActivityResultResponse(UnattendedJavaActivityRequest.java:67)
        at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute0(UnattendedJavaActivityRequest.java:55)
        at com.appiancorp.common.persistence.data.AppianDataUserContextProvider.executeWithConsistentDataReads(AppianDataUserContextProvider.java:143)
        at com.appiancorp.process.engine.ProcessContinuationRequest.executeOuter(ProcessContinuationRequest.java:68)
        at com.appiancorp.process.engine.ContinuationRequest.execute(ContinuationRequest.java:129)
        at com.appiancorp.process.workpoller.UnattendedRequestHandlerBean.onMessage(UnattendedRequestHandlerBean.java:36)
        at com.appiancorp.process.workpoller.WorkItem.run(WorkItem.java:110)
        at org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter.run(SimpleTaskWorkManager.java:241)
        ... 3 more
    Caused by: java.lang.ClassNotFoundException: javax.mail.Address not found by com.appcino.plugin.emlutility [47]
        at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1650)
        at org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
        at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2064)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
        ... 20 more

    Thanks,

    Dalyno

  • in reply to Arpit Pipersaniya

    Hello Arpit Pipersaniya, 

    I have the same issue that you say in your reply. Have you found any solution to that "There was an error creating the note" exception?

    Dhanyavaad.

  • in reply to keitht

    Hi Keith,

    We are facing the same issue and I was wondering if you found a solution for this?

    Cheers

    AP

  • in reply to anac0003

    Please select a value for setAvoidTxtAlternative parameter to resolve this error.

  • in reply to felipea0001

    was the issue resolved after the plugin upgrade?

  • v2.0.2 Release Notes
    • Further improved compatibility with emails using multipart/mixed content.

© 2024 Appian. All rights reserved.