2019.2

The Workflow configuration
The project's Workflow configuration contains just one process: an OL Connect Web process
(see "Web processes with OL Connect tasks" on page222).
Its NodeJS Server Input task has two HTTP Action entries: form and thank_you. This means
the process will be triggered when the server receives a request that ends with either /form or
/thank_you.
The request is saved to an XML file, which becomes the job file.
The Text Condition task checks if the request's header is thank_you. (For the function that is
used to read the header from the job file, see: XML data selections.)
If it is, the tasks in the branch run. The submitted data are merged with the thank_you Web
section and saved in Workflow's Data Repository.
Otherwise the main branch renders and returns the web form.
Note how the Section setting in the Create Web Content tasks determines which web page is
outputted (double-click the task to open the properties).
The Delete task is an Output task that does nothing, actually; it doesn't even remove anything.
However, this step is useful when running the project step by step in Debug mode. When it is
followed by another task, the Create Web Content task returns its output to the Workflow
process, where it can be viewed (click View as HTML).
The data mapping configuration
To extract the submitted data from the job file (the request XML), the process uses the data
mapping configuration: WEB_FORM Data.
To open it, select File > Open from the menu and browse to the Configurations\Resources
folder.
In order to create the data mapping configuration, the input data needed to be saved to a file
(see "Saving input as sample data" on page203).
The sample data file is located in the Configurations\Data folder, but you will also see it when
you open the data mapping configuration itself.
For more information about data mapping configurations see "The DataMapper" on page225.
Page 205