2020.1

Table Of Contents
page206 objects. In turn, MetaDocument objects hold "MetaDatapage" on page210 objects,
which have "MetaPage" on page213 objects.
In addition, a Node contains a collection of "Attributes" on page232 and can contain any
number of "Fields" on page233.
All of these objects are contained in a "MetaFile" below object, and they are obtained, directly
or indirectly, through methods of this object.
Note
In an OLConnect job, only the first three levels in the Metadata hold information about
the job: Job, Group and Document. A Group has information about a record set in the
Connect database and a Document has information about one record in that set. This
information appears in the Fields collection of the respective Node object. (When viewing
the Metadata file, this information is visible under 'User defined information'.) The Data
Model fields are added into the Document level.
Note
Be aware that changing the order and location of the various Node objects (except for the
Page object) within the Metadata structure, and/or setting the "Selected" on page219
property of a Node, may affect the output of a job (see "Including or excluding nodes from
the output" on page216 and "How Metadata affects the output" on page79).
MetaFile
The MetaFile object represents the physical Metadata file and is used to load and save the
Metadata from and to the file system. It also publishes the "MetaJob" on page200 object, which
is the root node of the Metadata structure.
The MetaFile object is the only object that is formally published to the user. All the other objects
are obtained, directly or indirectly, through methods of this object.
A standalone, empty MetaFile object can be created using CreateObject
("MetadataLib.MetaFile") in any script program, even outside of Workflow, or the {145E89F9-
C2DF-4604-821A-9BD6C4B468DA} CLSID with CoCreateInstance.
Page 197