2022.1

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 +
'.pdf';
The script uses a property: automation.variables.em_basic_workspace, which is defined in the
Preprocessor step. (See also: "Properties and runtime parameters" on page280.)
In this case, the variable holds the project's path. The order number in the path is extracted from
the sample data.
Note
In order to use the value of a Workflow variable - an 'Automation variable' - as a property
in the Preprocessor step, the property and the Workflow variable must have the exact
same name.
To see the script, click on the DeliveryNote field in the Data Model pane at the right; then take a
look at the Step Properties pane (in the middle).
To see where the property is defined, click the Preprocessor step on the Steps pane (at the left);
then look at the Properties section on the Step Properties pane.
Customizing the project
A project is a great starting point for building an OL Connect solution. This part explains how to
make changes to the project.
Do you intend to expand the project into a solution where Workflow runs on a different machine
that also has a different regional setting? Then indicate the desired encoding in the Designer
preferences (see "Sample Project deployment settings" on page912) before installing the
project.
Page 148