2022.1

l A template with an Email context. (See "Creating a template" on page477.)
l If the email should contain variable data, you may need to create a data mapping
configuration (see "Creating a new data mapping configuration" on page223). If the input
is going to be JSON data, you could add them to the design using a JSON file (see
"Adding JSON sample data" on page844).
Note that before templates and data mapping configurations can be used in a flow, they must
be sent to the OL Connect server separately. This can be done from the Designer (see
"Sending files to Connect Server or to another server" on page483) or in a startup flow (see
"OL Connect Startup flow" on page209).
An OL Connect print flow in Node-RED
This topic gives an overview of the nodes and files that are used in a typical OL Connect print
flow in Node-RED.
An easy way to create some example files to work with is to use a Sample Project. There are
two Sample Projects that create a sample print project; see "Sample Projects" on page1060.
For a print flow in Node-RED you would use all files except the Workflow configuration file.
If the objective of the flow is to serve a preview of a PDF, take a look at this topic: "An OL
Connect preview PDF flow in Node-RED" on page215.
The structure of a print flow
In its simplest form, a print flow may consist of only two nodes: one node that captures a data
file, such as a watch, watch-directory or read file node, and the OL Connect all in one node.
The all in one node combines the following four OL Connect nodes:
l The data mapping node that extracts data from a file and stores a record set in the
database, or the data get node that retrieves previously extracted data from the database.
o
The data mapping node needs a data mapping configuration, made with the
DataMapper (see "Data mapping configurations" on page222), and a data file of
course.
o
All the data get node needs is a Record Set ID.
Page 212