8.5
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.5
- System Requirements
- Basics
- Features
- The Nature of PlanetPress Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Variable Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
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 Design (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.
Processing
Aconnection to the selected database is made, the data is retrieved, and an output in the selected
emulation format is generated.
Output
The result of the query is output in the selected data format. The current emulation is changed to the
selected format. Metadata and jobinfos are not modified in any way.