7.3

l The script editor text box:This is where you enter your XSLTScript that will be used. If you use an external script
file, this will display the content of the file (note however that modifying the script in this case does not modify the exter-
nal file and changes are not saved).
l Script running from:Choose if the script should be run from the editor text box, or from an external script file.
l Script filename and path:Either enter the full path of the XLSTScript, or click the Browse button to navigate to
the file. This option is only available if you choose external script file in the Script running from option.
PlanetPress Database
PlanetPress Database action tasks retrieve 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.
PlanetPress Database 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 "Initial and Sec-
ondary Input Tasks" (page n)). 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 Database action task to gather your actual data.
PlanetPress Database action tasks require version 2.5 or higher of the Microsoft Data Access Components (MDAC),
including JET 4.0.
When adding a PlanetPress Database action task, you have two options:
l You can use static properties (properties that will remain the same regardless of the data processed at runtime). 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 Suite Workflow Tools (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 runtime). 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 Suite Workflow Tools. Note that this option will not let you test the query performed by this task before it is
performed with actual data.
PlanetPress Database action task properties are as follows:
Database Connection tab
l Database group
l Location: Enter either the path and name of the database or a database connection string in this box. You may
click to navigate to the database and paste the database path and name automatically to this box. You may also
click create an ODBC connection string to the data source and paste the string automatically to this box. If a
login name and password are required to connect to the database, a dialog box is displayed and the information
you enter is saved in the configuration of the PlanetPress Database action task.
l Table/Query: Select the table or query containing the information you need as your input data.
l Range group
l All: Select this option use all the records included in the database.
l Records: Select this option use only some of the records in the database. Indicate the range by entering the
number of the first record followed by a dash and the number of the last record. To use records 50 to 75, for
example, enter 50-75. Note that this option is intended mostly for testing purposes, since in real life scenarios,
you typically want to use all the records stored in a database.
l Emulation group:Use options from this group to customize the data file generated by the PlanetPress Database
action task.
©2010 Objectif Lune Inc - 132 -