8.7

Table Of Contents
Input
A PDFFile, either with no metadata and along with metadata that presumably corresponds to
the PDF file, or a PDFfile with embedded metadata.
Processing
If the Embed option is used, the metadata information is embedded directly into the PDFFile as
binary data. This does not change the way the PDFis viewed by any PDFviewer.
If the Extract option is used, metadata present inside of the PDFfile is extracted from it. If no
metadata is embedded, the task generates an error W3976.
Output
The PDFfile with embedded metadata (the metadata is not deleted from the PDFFile on
extraction, so this task will always output a PDFwith embedded metadata).
Properties
General Tab
l Extract metadata into PDFjob file:the metadata is extracted from the current data file
(which is assumed to be a PDF file in which metadata has been previously embedded),
and it becomes the current metadata from this point on, overwriting any current metadata
file that may already be set.
l Embed metadata from PDFjob file:the current metadata file is inserted in the current
data file, which is assumed to be a PDF file. If the original PDF is PDF/X or PDF/A
compliant, the resulting PDF filewill also becompliant.
On Error Tab
The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog"
on page731.
By default, any action task, branch, splitter or condition that generates an error will simply be
ignored, and the task just under it (not within a branch)will be given control of the job file
without any modification. Any initial input task that generates an error will stop the process from
running as a whole, and output tasks will not generate output. The On Error tab can be used to
overwrite the default behaviors.
Page 498