7.5

l SQL Statement:An SQLstatement that is understood by the database you are using and that will return a
series of records that the Microsoft® Word® template is expecting. Note that no validation is made on
SQLstatements except if they are for Microsoft Access and Excel data files. You can use the Test Connection but-
ton to test the SQLand connection string.
l Test connection: Checks if the Connection String and SQLStatement are valid, and if the resulting recordset
is understood by the Microsoft® Word® document. This is optional, though highly recommended.
l Output Type:
l .PDFFile (with metadata):The result will be a PDFfile with the number of pages generated by the com-
bination of the template and recordset. Metadata is also included that complement the PDF.
l .DOCfile:The result is a Microsoft® Word® document in .doc format. Note that this format is not supported
by PlanetPress Suite as a data file or job file, so this option is only useful if you are simply planning to save the
Word document in a specific location.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are overwritten.
Common Errors
Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are
related more to the system than to PlanetPress itself. Some examples would be W3813, W3830, W3991, W4005. These cor-
respond to issues such as not having any space to write files, permission errors on folders or files, etc.
Comments Tab
The Comments tab, added in PlanetPress Suite 7.5, is common to all tasks. It contains a single text area (Task
comments)that lets you write comments about the task. These comments are saved when the dialog is closed with the
OKbutton, and are displayed in The Task Comments Pane.
Notes
l Microsoft Word must be installed on the PlanetPress Suite Workflow Tool system.
l Microsoft Word must not be currently opened when the automation task runs.
l Microsoft Word 2003 and up are supported.
l The task uses a printer queue set with the “PlanetPress Word to PDF Printer” driver, which is created and set by default
on-the-fly the first time a Microsoft® Word® Document to PDFAction Task is run. This printer cannot be shared on the
network in order to avoid confusion from network users, however it is shared between all Microsoft® Word® Doc-
ument to PDFaction tasks on the same system.
l While debugging this task, the printer shows the message that the document can not be printed. This message is nor-
mal and will not appear when running a live configuration.
l If using a Microsoft® database such as Access® or Excel®, each software must be installed in the same version. For
example, using Microsoft® Word® 2007 with a Microsoft® Access® 2003 database will cause the task to fail.
l If the database path is specified in the Microsoft® Word® document, the mail merge has to be performed with the set-
tings specified in the document, otherwise the database path provided in the task is ignored and can cause different con-
flicts. To use custom settings, the Microsoft® Word® document should contain only mail merge fields with no database
path entered. The Microsoft® Word® to PDF Action task allows specifying the path of the database and the query to
use. The Use custom settings option is very usefully for using different databases and queries in a single process.
l If the database is the same for 2 processes, one of two processes aborts. Each process has to use different databases,
or no more than one process with a Microsoft® Word® to PDF task.