8.4

l Open options :
l Zoom factor: Fit in window
l Default view: Page only
Database Query
Database Query action task retrieves data from various databases to use as input data. The data received
by the task may be kept as is or converted to the CSV, Fixed Length Columns or XML format.
Database Query action tasks are not considered input tasks as such, because they cannot be used to start
a process. Although they cannot be used to get the process’ initial input, they can be used to gather
secondary input (see "Input Tasks" on page 156). In cases where all your data comes from databases, you
can use a Create File input task as a dummy task at the beginning of your process, and then use a
PlanetPress Workflow Database action task to gather your actual data.
Technical
Database Query action tasks require version 2.5 or higher of the Microsoft Data Access Components
(MDAC), including JET 4.0.
When adding a Database Query action task, you have two options:
l You can use static properties (properties that will remain the same regardless of the data processed at
run-time). This option lets you use an Open DataBase Connectivity (ODCB) compliant data source.
You can also edit the SQL statement that assembles the database table. Note that you can import a
database connection configuration that you previously exported from PlanetPress Connect (when you
created a document) or from PlanetPress Workflow (when you set up a sample data file for a process).
l You can use dynamic properties (properties that include variables or data available at run-time). This
option lets you create a dynamic database connection string as well as an SQL statement that
changes based on the data processed by PlanetPress Workflow. Note that this option will not let you
test the query performed by this task before it is performed with actual data.
Input
Any data file. The data file will be discarded by the task.