2021.1

'.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256.)
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 "Project Wizard deployment settings" on page861) before installing the
project.
Input data
If your input data is in a file, but the file is of a different type or has a different structure, create a
new data mapping configuration to match it. (See "Creating a new data mapping configuration"
on page198.)
When it's finished, send the new data mapping configuration to Workflow (see "Sending files to
Workflow" on page446).
Then open the Workflow configuration, double-click the Execute Data Mapping task to open it
and select the new data mapping configuration.
Page 144