Skip to main content Skip to complementary content

Procedure

Procedure

  1. Drop a tFileInputMail and a tLogRow component from the Palette to the design workspace.
  2. Connect the two components together using a Main Row link.
  3. Double-click tFileInputMail to display its Basic settings view and define the component properties.
  4. Click the [...] button next to the File Name field and browse to the mail file to be processed.
  5. Set schema type to Built-in and click the [...] button next to Edit schema to open a dialog box where you can define the schema including all columns you want to retrieve on your output.
  6. Click the plus button in the dialog box to add as many columns as you want to include in the output flow. In this example, the schema has four columns: Date, Author, Object and Status.
  7. Once the schema is defined, click OK to close the dialog box and propagate the schema into the Mail parts table.
  8. Click the [...] button next to Attachment export directory and browse to the directory in which you want to export email attachments, if any.
  9. In the Mail part column of the Mail parts table, type in the actual header or body standard keys that will be used to retrieve the values to be displayed.
  10. Select the Multi Value check box next to any of the standard keys if more than one value for the relative standard key is present in the input file.
  11. If needed, define a separator for the different values of the relative standard key in the Separator field.
  12. Double-click tLogRow to display its Basic settings view and define the component properties in order for the values to be separated by a carriage return. On Windows OS, type in \n between double quotes.
  13. Save your Job and press F6 to execute it and display the output flow on the console.

Results

The header key values are extracted as defined in the Mail parts table. Mail reception date, author, subject and status are displayed on the console.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here