2022.1

to be stored somewhere where the print flow can access them, in order to retrieve the
Print Content Items. You could for example use MongoDB.
Retrieving the output
The print output node outputs two things: the ID of the output location in the File Store and an
array containing the output file(s). Connect the print output node with the OLConnect file
download node to download a ZIP archive of the entire job based on the msg.managedFileId
provided by the print output node. The data is read into a data buffer which allows it to then be
written to disk using the write file node.
The target location can set by entering the full path in the Filename field of the file node. The
other option is to set it dynamically in msg.filename, using a change or function node.
Downloading individual output files
The array that the print output node outputs can be used to download the files individually.
You will need a split node to iterate over the array in msg.payload and generate a new
message for each file, setting msg.payload to the respective file name. See "Iterating over items
in an array" on page208.
Make sure to clear the Filename field in the write file output node before deploying the flow. A
value configured in the node takes precedence over the msg property - msg.filename in this
case - and will be used for every file, overwriting the previous file.
Files used in a print flow
Before creating a print flow, you will need to create:
l A template with a Print context. (See "Creating a template" on page477.)
In addition, the flow may use:
l A data mapping configuration, if the documents should contain variable data that is
extracted from some data source. (See "Creating a new data mapping configuration" on
page223.)
l A Job Creation Preset. (See "Job Creation Presets Wizard" on page1230.) A Job
Creation Preset defines where the output goes and makes it possible to filter and sort
records, group documents, and add metadata.
Page 214