2.90:Content Action

Content Action is an Activity providing additional functionality for multi-page file formats (PDF and TIF files) through one of five actions: Split, Merge, ClearChildren, ClearContent, RepairPDF.

Most commonly, this Activity is used to split multipage documents in a Batch, creating child Batch Page objects for each page in the file (using the Split action). This Activity is also used to merge child Batch Pages and Batch Folders into a multipage file, stored on the parent Batch Folder (using the Merge action). Though less common, there is additional functionality to delete child objects (using the ClearChildren action), remove a PDF file from a Batch Folder (using the ClearContent action), and repair a PDF file (using the RepairPDF action).

About

The Content Action activity manipulates the content files of a Batch Folder in a Batch, either a native file stored on the Batch Folder (typically a multipage PDF or TIF file) or the Batch Folder's child folder and page objects. What happens is determined by its Action property. This can be one of five choices: Split Merge ClearChildren ClearContent RepairPDF Each Action option has its own property configuration options (with ClearChildren, ClearContent, and RepairPDF having no further configuration required).

Split

Split

The Split Action is the most commonly used functionality for the Content Action activity. It will split out the pages of an imported multipage PDF or TIF file. When PDF files are imported into a new Batch, a Batch Folder object is created for each multipage PDF file imported. The PDF file is stored as the "native file version" of the Batch Folder. It lives in the file store location associated with the Batch Folder (or in layman's terms it lives "on the document folder"). However, what if Grooper needs to process each page instead of the full document? It needs a page-level object to do page-level processing. This is what the Split Action accomplishes. It takes that native file living on the Batch Folder and creates child Batch Page objects from it, one Batch Page object for each page in the native multipage file.