2022.2

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.
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175 property of a
Node, may affect the output of a job (see "Including or excluding nodes from the output" on
page173 and "How Metadata affects the output" on page70).
Note: When timestamps are processed as strings (as in the Workflow Metadata), and if they are
being parsed manually, keep in mind that date strings conforming to ISO 8601 or expressed in
milliseconds (Unix epoch time, for instance 1611607555000) are stored as UTC timestamps in
the OLConnect database. In the output, they are written as ISO 8601 date string values: YYYY-
MM-DDTHH:MM:SSZ.
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 page165 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.
The current job's Metadata file name can be obtained using the Watch.GetMetadataFilename method
(see "Watch.GetMetadataFilename" on page137) when using the "Run Script" on page426 task. Note
that the exact syntax may vary according to the selected script language.
When writing a plugin using the plugin SDK the current job's Metadata file name can be obtained by call-
ing the IWatchJob::MetadataFilename method from within IWatchPlugin::Execute.
Caution: Under no circumstances should any other objects of this library be created directly.
Always use the published APIs to create new objects.
The Metadata objects point to an underlying persistent data store. This means that if there are
live references to Metadata objects and the underlying data is destroyed (e.g. a new file is
Page 163