7.2

Digital Action Task Properties
Digital Action action tasks use PlanetPress Image to generate the same types of documents generated by PlanetPress Image
output tasks. Since Digital Action tasks are not output tasks, the documents they create are typically passed on to the following
task. The image files they generate are always saved, along with their index files (if any), to an archive folder.
The Digital Action task requires a PlanetPress Imaging license to be present on the same IPSubnet as PlanetPress
Workflow, either on the same server or a different one with PlanetPress Image installed and activated.
The properties of the Digital Action Action Task are precisely the same as the PlanetPress Image Connector Task. See "Plan-
etPress Image Output Task Properties" (page 179) to see a list of these properties.
Differences between Digital Action and Image tasks:
l Digital Action is an Action Task and cannot be the last task in a branch or process. Image is an output task, and has to
be placed at the end of a process or branch.
l In PlanetPress Workflow 7.2.4 and older, Digital Action does not update the PlanetPress Search Database, even if a
PDIis generated and even if the option is checked in the preferences. This behavior was changed starting in Plan-
etPress Workflow 7.3.
l Digital Action can accept PostScript (.ps)files as an input, even if they are not generated by any PlanetPress tools.
Links in the Image Generation Process
Since PlanetPress Image lets you create image files via output tasks as well action tasks, and since it can also be used to gen-
erate files using proprietary formats, various software may be involved in the process.
l PlanetPress Suite Workflow Tools: This is where the process is initiated either via a PlanetPress Image output task or
via Digital Action actions tasks. When you add a PlanetPress Image output task or a Digital Action action task to a proc-
ess, you configure the task’s properties, which include for instance, the address of the computer running PlanetPress
Image and the name of the PlanetPress Design document to use. As you may remember, there are few differences
between PlanetPress Image output tasks and Digital Action action tasks. Only PlanetPress Image output tasks provide
emailing options. Digital Action action tasks cannot be placed at the end of a process and are only considered com-
pleted when the actual image generation process is finished.
l PlanetPress Image service: This is where the image file is actually prepared and sent to the archive folder or message
recipient. You can configure the PlanetPress Image service either via the PlanetPress Suite Workflow Tools Con-
figuration program.
l PlanetPress Suite Workflow Tools Imaging plugins: These optional plugins are used to create files that use proprietary
formats, such as AutoStore from Notable Solutions.
XML Index File Structure
PlanetPress Image generates a standard UTF-8 encoded XML file that has the following structure and content
Name: Value:
<Pdi>
</Pdi>
Each generated XML file has Pdi tags wrapped around its content. This indicates the source of the enclosed
XML content is the PlanetPress Suite.
<Header>
</Header>
These tags wrap around the header information of the XML file. The header information contains the name of
the variable content document used, the name of the archived XML file, the date and time the file was proc-
essed, as well as the output type called the archive method.
<FormName>
</FormName>
The name of the converted document (in the PlanetPress Suite Workflow Tools Documents folder) the Digital
Action action executed to generate this XML file and its associated PDF, or other type of image output.
©2010 Objectif Lune Inc - 185 -