8.4

Properties
General tab
l Microsoft Word Document: Enter a Microsoft® Wor document or template, or click the browse button
to navigate to the location of the document. The supported extensions are: *.doc, *.docx, *.dot and
*.dotx.
l Perform Mail Merge: Check when providing a Microsoft® Wor document or template configured for
mail merge.
l Use settings specified in document: Selected to instruct the task to use the connection string
and SQL statements stored in the DOC file. There is no guarantee that the database, connection
string or statement are still valid, especially if the DOC file was moved or sent to someone else.
l Use custom settings: Override the mail merge settings in the Microsof Word® document and
lets you specify your own.
l Connection String: The connection string to any ODBCdatabase supported by PlanetPress
Workflow. You can use the Browse button to open an existing File DSN, or use the Database
Button to open the ODBCconnection interface.
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 button 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 Microsof Word® document. This is optional, though
highly recommended.
l Output Type:
l .PDFFile (with metadata):The result will be a PDFfile with the number of pages generated by
the combination of the template and record set. 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 Workflow 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" on page 587.
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