receive_text_jobtype.cfg

The RICOH ProcessDirector-supplied SetJobTypeFromRules step can use the receive_text_jobtype.cfg control file to set the workflow from the jobID.overrides.text file. The step can also use this control file to convert an optional Job Definition Format (JDF) job ticket file, jobID.overrides.jdf, to a temporary text-based overrides file that it can use with the jobID.overrides.text file to set the workflow.

All the information in the control file is case-sensitive.

The control file contains these sections:

CONFIGURATION section

This is a global settings section consisting of keywords that define how RICOH ProcessDirector interprets the job ticket parameters.

FILE_MODE

This keyword controls how RICOH ProcessDirector processes the job ticket. A value of "FILE" instructs RICOH ProcessDirector to treat all the information in the file as a single record. In this mode, RICOH ProcessDirector can do search and replace actions. The double quotation marks in the value are required.

A value of "RECORD" for the file mode causes RICOH ProcessDirector to read the information in the file on a record-by-record basis. The double quotation marks in the value are required.

ATTRIBUTE_PATTERN

This keyword specifies a regular expression that defines how RICOH ProcessDirector recognizes the names of properties. As supplied by RICOH ProcessDirector, the value is "\$\{Job.*\}". The double quotation marks delimit the expression and the backslash characters are escape characters that precede the special characters in the expression.

The "\$\{Job.*\}" value instructs RICOH ProcessDirector to recognize property names as strings that begin with Job. and that are followed by zero or more characters. RICOH ProcessDirector job property names match this convention, such as Job.Duplex and Job.Print.CumulativeSheetsStacked.

KEYWORD_CASE

This keyword defines the case of the characters in the job ticket parameter names. Depending on settings on the sending system, parameters might be passed as all uppercase or all lowercase characters. Use a value of "UPPER" or "LOWER" based on the requirements of the installation.

Delimit the beginning and ending of the CONFIGURATION section with CONFIGURATION and ENDCONFIGURATION.

REPLACE section

This section uses sed commands to replace strings in the job ticket. It is commented out in the sample file. You will probably not need to use it.

Delimit the beginning and ending of the REPLACE section with REPLACE and ENDREPLACE.

PATTERN KEY_VALUE section

This section describes how RICOH ProcessDirector finds keywords and values, and converts them into tokens by using regular expression groups. As supplied by RICOH ProcessDirector, the section looks like this:

PATTERN KEY_VALUE
"(.*?)=(.*?),"
ENDPATTERN

The pattern is delimited by double quotation marks and the pattern to the left of the equals sign represents the keyword. The pattern to the right represents the value. This pattern creates a comma-delimited list of keyword and value pairs.

DEFINE statements section

This section uses symbol formulas to set the RICOH ProcessDirector workflow from a value in the job ticket that was passed with the job. This is the type of DEFINE statement that RICOH ProcessDirector typically uses to set the workflow:

DEFINE ${Job.JobType} AS "Transform"
DEFINE ${Job.JobType} AS "PDF" WHEN (${Job.InputDatastream} == "pdf")

The first DEFINE statement sets the default workflow. The second DEFINE statement is conditional. In this example, RICOH ProcessDirector sets the value of the Job.JobType property to PDF when the value of the Job.InputDatastream parameter in the text overrides file is pdf. If the Job.InputDatastream parameter has any other value, RICOH ProcessDirector uses the default workflow.