Email Import (Office 365) - Infiniworx - Foundation 23.1 - Foundation 23.1 - AnyDoc - external

Infiniworx

Platform
AnyDoc
Product
Infiniworx
Release
Foundation 23.1
License

This tool is used to import emails using the OAuth2 authentication into the workflow. You must first register the OAuth2 application with Azure before you can import emails. See OAuth2 Authentication for instructions on registering the application.

Job Objects (Out)

Description

EML File

The name of the job object containing the original email in the EML format.

Email Body Text

The name of the job object containing the text of the email body.

Email Body Image

The name of the job object containing an image of the email body. Configure the Image Creation setting of this tool to specify how the email body image is created.

Options

Description

Image Creation

Select an option to specify how the image of the email body is created:

  • Both: The email body is saved as both a multi-page TIFF and a series of single-page TIFFs for each page of the email body.

  • Multiple Pages: The email body is saved as a multi-page TIFF.

  • None: No image is created.

  • Single Pages: Each page of the email body is saved as an individual single-page TIFF.

Remove Email Headers

Set to True to remove the header information from the email. Set to False to retain the header information.

Server Settings

Description

Setup

Set up the email server. See Setting Up the OAuth2 Email Server.

Data Fields

Description

Body

Link the content of the body to a data field.

CC

Link the names carbon copied to a data field.

From

Link the name who sent the email to a data field.

Time Stamp

Link the time stamp of the email to a data field.

To

Link the name who received the email to a data field.

Subject

Link the subject line to a data field.

Headers

Description

Mappings

Configure the tool to capture any number of email headers, including custom headers, and map them to data fields to be used in the workflow. The names are case-insensitive. All of the standard header names are supported as well as any implementation specific headers.