2021.1

l The Folder Capture task reads the project's Workspace path from a global variable. The
value of that variable is set by the project wizard when it installs the project.
l The Execute Data Mapping task extracts data from the sample data file and outputs
them in the Metadata.
l The Create Email Content task creates the emails, using the Metadata as data source.
Note that it sends the emails in test mode, which means it will send the emails to the
sender.
The settings on the Email Info tab are taken from the project wizard.
l The Delete task is an Output task that does nothing, actually; it doesn't even remove
anything. This step is sometimes useful when running a project step by step in Debug
mode, as it forces preceding tasks to return their output to the Workflow process. The
Create Email Content task, however, does not return the generated emails to the
Workflow process.
The data mapping configuration
The Workflow process uses a data mapping configuration, made with "The DataMapper" on
page196: EM_BASIC Data.
To open the data mapping configuration, open the Designer, select File > Open from the menu
and browse to the Configurations\Resources folder.
This data mapping configuration will of course only work with the appropriate data files. It was
designed for XML files that are structured like this file: Sample Data.xml (in the
Configurations\Resources\Data folder).
The sample data yields 5 records with customer data including a detail table with invoice
details.
Much of the information in the extracted records isn't used in the email, but was used to create
the delivery notes.
The email addresses are used in the template (in the To field), but ignored in the Workflow
process because it sends emails in test mode (see "The Workflow configuration" on the
previous page).
Using a Workflow variable
The path to the delivery note is constructed via JavaScript:
automation.variables.em_basic_workspace + '\\Delivery Notes\\' + record.fields.OrderNumber +
Page 143