2022.2

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199),andadatafileofcourse.

o
Allthedata getnodeneedsisaRecordSetID.
l
Thepaginated contentnode.Thisnodemergesthedatawithatemplate,resultinginPrintCon-
tentItems.TemplatesaremadewiththeDesigner(see"Templates"onpage414).
l
Thepaginated jobnode.ThisnodeturnsasetofPrintContentItemsintoaprintjob.Anyjobset-
tingsarepassedonviaaJobCreationPresetwhichismadewiththeDesigner(see"Job
CreationPresets"onpage1322).
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1324).
ThenodeslistedhereareOLConnectnodes;see"OLConnectnodes"onpage182.
TheOLConnectnodesarebuiltarebuiltinsuchawaythattheoutputofanodeisautomaticallyrecog-
nizedasinputbythenextnode.
l
Thedata mappingnodeoutputsadatasetIDinmsg.dataSetIdwhichisusedbythepagin-
ated 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"NodesusedinOLConnectflows"onpage185.
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:
Page 192