2022.1

l The paginated content node. This node merges the data with a template, resulting in
Print Content Items. Templates are made with the Designer (see "Templates" on
page477).
l The paginated job node. This node turns a set of Print Content Items into a print job. Any
job settings are passed on via a Job Creation Preset which is made with the Designer
(see "Job Creation Presets" on page1538).
l The paginated output node. This node creates the actual output file(s) and stores them
in the File Store. Any settings that it needs are passed on via an Output Creation Preset
which is made with the Designer (see "Output Creation Presets" on page1540).
The nodes listed here are OL Connect nodes; see "OL Connect nodes" on page200.
The OL Connect nodes are built are built in such a way that the output of a node is
automatically recognized as input by the next node.
l The data mapping node outputs a data set ID in msg.dataSetId which is used by the
paginated content node to retrieve the data and create a set of content items.
l The paginated content node outputs a content set ID in msg.contentSetId which is used
by the paginated job node to create a print job.
l The paginated job node outputs a job set ID to msg.jobSetId which is used by the
paginated output node to generate output.
To build the flow you also need some nodes that are available by default or have been made
by other parties. See "OL Connect automation with Node-RED" on page200.
The all in one node is the fastest and most efficient way to create print output, as in that case
multi-threading is supported: the data set and content items are produced in parallel.
The separate nodes would be of use in situations like the following:
l The record set, created by the Execute Data Mapping task, is also needed to create
another kind of output in the same flow.
l The input is JSON data which can be used directly and doesn't need to be stored in the
database. In this case there is no need to use the data mapping node or data get node.
l The Print Content Items have already been created, either in the same flow or in another
flow. Print Content Items can be retrieved from the OL Connect database using the data
get node. Subsequently, the paginated job and paginated output nodes can generate
print output from them.
Note that at the time the Print Content Items are created, their Print Content Set ID needs
Page 213