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
In PlanetPress Design:
1.
Use a Set Job Info action task and associate a variable with the job’s name.
2. In the output task, make sure to select the option that adds the job information to the
document.
In PlanetPress Connect:
l Somewhere at the bottom of each document page, add a Data Selection object defined
as a custom data selection that contains a reference to the job info variable sent from
PlanetPress Workflow and a current page marker.
You can use, for example, =&watch.jobinfos[6]+'-'+intostr(¤t.datapage)'
Debugging your PlanetPress Workflow Process
Debugging a process is separated in two parts. The first part is designing the process, which is
to add the different tasks, branches and conditions to the process and configuring them. The
second step is testing whether or not the process and configuration actually work.
Before debugging begins, the following prerequisites must be completed:
l There must not be any Unknown Tasks in the process.
l Asample data file must be selected. To choose a sample data file, click the Select button
in the PlanetPress Workflow Ribbon's Debug tab and browse to a valid sample data
file. Alternatively, if a document present in the configuration contains the necessary data
file, it can be attached to the process easily. See Use Data and Metadata Files Attached
to Documents.
When debugging your process, it is important to keep in mind that:
l
The Initial Input task is never executed. The sample data file is used instead of the initial
run. This is to prevent "live"data from being retrieved by the initial input task while
debugging is being done. If, however, the initial task is critical to the process, it can be
executed by copying the initial input task and pasting it as a secondary input task (the first
action task to actually run in the process). Do not forget, however, to remove this duplicate
task before saving the configuration!
Page 53