Specifications

The intent of this feature is to allow you to verify values from XML/JDF job ticket file are defined
correctly and to ensure logic defined within Rule Based variables work as expected. This dialog
does not change any settings within a variable.
To check a Variable Set select the Tester icon in the Enfocus Variable Set Editor. All the variables
within the current Variable Set will be displayed with the values currently defined along with the
last XML/JDF job ticket loaded (if any).
Within the Enfocus Variable Set Tester, you can Browse to load a sample XML/JDF job ticket file.
By default, the last file loaded is displayed. Below the Sample Job Ticket, the current variables
are listed on the left with the values returned from the loaded job ticket for each variable displayed
on the right.
If a new job ticket is loaded the values that will be returned from that job ticket are displayed, this
functionality enables you to easily test your variables against different sample files to check the
expected results will be returned to the preflight profile.
Job Ticket variables and their values will be displayed based on the file loaded along with the XPath
defined and any modifications to that field based on the variable settings. If there is an error in the
XPath or if the variable does not exist in the sample XML/JDF file, the variable will display in Red.
Errors in job ticket values may be the result of errors in any manipulations defined or errors in
the XML/JDF sample file. Errors in the XPath or manipulations can be corrected by editing the
offending variable.
Rule Based variables that use Job Ticket values to trigger values will change based on the sample
job ticket file loaded. These values are not editable within the Tester.
Constant variables and Rule Based Variables that use Constant variables defined in PitStop Pro
will be displayed and the Constant variables can be modified for testing. However, PitStop Server
will only use the default value from the Constant variable when processing jobs.
Troubleshooting for Smart Preflight
Following table lists how to fix some issues you may run across while working with Smart Preflight.
FixProbable CauseIssue
Review the variable and ensure
it's defined as the right "type"
Variable "type" does not match
the type of preflight check or is
Variable not available to apply
to a preflight check
(Number, Length, String orentered in differing Variable Set
than currently selected Boolean) to match the preflight
check or check to make sure
the correct Variable Set is
selected
Smart Preflight settings under
Hot Folder set-up for that
Variables we're used in the
preflight profile that are not in
Hot Folder workflow won't
activate with Smart Preflight
enabled workflow and ensure you have
the correct Variable set
selected
your active Variable Set for that
workflow
Regular Expressions
Regular expressions, or "regexps", provide a way to find patterns within text. This is useful in many
contexts, for example a regexp can be used to check whether a piece of text meets some criteria.
For more information, refer this http://www.roblocher.com/technotes/regexp.aspx website.
58
Enfocus PitStop Server