7.0

Every process created with PlanetPress Watch/Server Configuration begins with an input task and ends with at
least one output task. In its simplest form, a process can simply retrieve data from a given folder and save it
in a different folder. In most cases, though, processes are more elaborate and configurations, which may
include many processes, can be extremely complex.
Not only can PlanetPress Watch/Server play the role of a data hub, receiving and forwarding data files, but it
can also perform various operations both on the data and with the data.
Processes may include nodes from which the process branches out to accommodate multiple output tasks.
Some nodes may be conditional and others not.
A) From this node, the process branches out two ways. A copy of the input data is sent down both branches in all cases.
The Send To Folder task is always performed. B) From this node, the process branches out only one way. C) The data is
sent down this branch if the condition is true (if the other printer is out of paper, for example). D) The data is only
handed if the above condition is false.
When PlanetPress Watch/Server comes to a node where a non-conditional branch starts, the flow is diverted
to the non-conditional branch. When the tasks found on the non-conditional branch have been performed, the
flow goes back to the main branch and its tasks are then performed. Note that the same job file is sent down
the main branch and the non-conditional branch.
When PlanetPress Watch/Server comes to a conditional branch, the flow either stays on the main branch or is
diverted to the conditional branch based on how the condition is resolved; the tasks found on the other branch
are not performed.
All tasks can exchange data between themselves, regardless of the process in which they are included. In
other words, an output task from process X can provide data to an input task included in process Y. A send to
Folder task can, for instance, store data in a folder watched by a Folder Capture task included in any process.
Note that the same can be achieved within a single process using a secondary input task (bear in mind that
the fewer processes your configuration has, the easier it is to manage).
Processes and Schedules
Each PlanetPress Watch/Server process has its own schedule, which determines when the process is to run,
and therefore when its tasks are to be performed. If an input task from a given process requires data from an
output task included in another process, you should therefore take into account each process’ schedule.
Multiple input tasks should not be competing for the same data. In other words, processes that run at the
same time should not take the same data from the same source. There are many ways that you can prevent
such situations from happening:
• For those input tasks that let you determine which files should be taken from the source location, use
different criteria. You could have two Folder input tasks, one that retrieves files with a txt extension and
one that retrieves files with a .htm extension, for example.
Understanding PlanetPress Suite Workflow Tools - Key Concepts
Objectif Lune Inc. © 2009 10