2022.2

# Do something with Job Info 9!
Watch.Log("Job Info 9's value is: " + s,5)
Perl
In PERL, die stops execution of the script unless the unless command is used, but in order to raise
an exception and trigger the On Error tab, you must nest the die command inside an eval statement.
See the perl documentation.
$s = $Watch->GetJobInfo(9);
if ($s eq "") {
eval {die "Value cannot be empty!"};
} else {
# Do something with Job Info 9!
$Watch->Log("Job Info 9's value is: ${s}",4);
}
Special workflow types
PlanetPress Workflow supports multiple input and output types, in so many different combinations that
it would be hard to give example processes for each possibility. However, some types of processes like
PDF and HTTP processes, and processes related to another product, are important enough to pay
some attention to them.
This chapter will describe each of these special workflow types and give at least one example of an
implementation that uses them.
Note: Typical OL Connect workflows are described in PlanetPress Connect's Online Help; see
Workflow processes in OL Connect projects.
HTTP Server workflow
An HTTP workflow receives requests from a client via a GET or POST request, sometimes only with
information, sometimes with attached files. An HTTP workflow is basically an XML workflow since that
is the type of file created by the HTTP Server Input task. See the "HTTP Server workflow" on the
facing page page for more details.
OL Connect Send processes
Connect Send allows for PostScript files to be received over the internet from any Windows Desktop
application. It is in fact an application with two components. The first is a Windows printer driver while
the other is a group of Workflow plugins (Job Processor, Get Job Data and Get Data). These two com-
ponents work together indiscriminately, each needing the other to function.
Page 220