2021.2

AlambicEdit API reference
The AlambicEdit library allows Workflow to access, create or modify PDF files. It does so by
wrapping Adobe PDF Library API calls in an object-oriented COM API. The use of COM as the
underlying technology allows Workflow's scripting environment to create an instance of that
COM object through the Watch.GetPDFEditObject method (see "The Watch Object" on
page156).
The object's hierarchy is modeled on the PDF document structure:
l The PDF object implements the IPDF interface. This interface defines methods to open,
close and save files, as well as to access meta information such as the XMP attachment.
The interface also implements a Pages collection object to access the list of pages in the
PDF. (See "PDF object" on page245.)
l The Pages collection object implements the IPages interface. This interface defines
methods to add, import, move or delete pages as well to access individual Page items.
(See "Pages collection object" on page257.)
l The Page object implements the IPage interface. This interface defines methods to
retrieve information from a page or modify it. A page may also be drawn on a Windows
Device Context (DC), but note that access to DCs may not be available in all scripting
languages. (See "Page object" on page262.)
"IPdfInfos" on page273, "IPdfPrintParams" on page274 and "IPdfRect" on page275 are the
structures used.
Note
In OL Connect, PDF files are normally best handled by "OL Connect tasks" on page591.
However, the AlambicEdit API can provide a solution in special situations; see for
example Stamping one PDF file on another PDF file.
Syntax conventions
The syntax for methods, properties and structures is as follows.
Page 243