Apogee Help : Processing Task Processors : Conditional : Conditional Decision Settings
Conditional Decision Settings
This dialog box allows you to configure the Conditional settings.
You can access these settings:
When creating Parameter Sets (see “Managing Parameter Sets”). Here, you will see a ‘Lock in Production Plan’ check box (selected by default). If this check box is selected, the settings will be initially locked in the Settings pane. If this check box is deselected, the settings can be edited in the Settings pane.
In the Settings pane, in the Plan tab of the Job Manager and the Ticket Editor. The settings may be initially locked, as indicated by the Lock icon. If you edit the job, you can unlock them as described in “Settings Pane (Ticket Editor)”.
Name
The name of the Parameter Set as it will appear in the Production Plan. When you create a Parameter Set, you should specify a Parameter Set name. You can always change this name later by editing the job, choosing the Parameter Set from the Task Processor in the Plan tab, and unlocking the settings in the Settings pane.
Test
Pattern Match
The Conditional Task Processor will process PDF files based on the result of the specified patterns.
Preflight Action
The Conditional Task Processor will process PDF files based on the result of the specified Enfocus PitStop Preflight Action.
Preflight Profile
The Conditional Task Processor will process PDF files based on the result of the specified Enfocus PitStop Preflight Profile.
Direct
You have two options:
Entire document
The condition is applicable for all the pages of the document. If one of the pages does not match the condition, the complete document will fail.
Individual pages
The condition is applied on a page-by-page basis. Only the pages of the document that do not match the condition will fail, the other pages of the document will pass. This setting will process slower.
Send to top when
The content of this field depends on your Test selection (see above). You may have selected Pattern Match, Preflight Actions or Preflight Profiles. This option determines how the Conditional Task Processor combines the outcome of the individual tests. You have the following options:
All tests pass
All tests fail
At least one test passes
At least one test fails
Pattern match
Pass when
If you have selected Pattern match, you have two options:
At least one pattern matches: The documents or pages are sent to the upper flow when at least one pattern matches.
All patterns match: The documents or pages are sent to the upper flow when all patterns match.
Match
This field defines the text to match, expressed in the form of a variable or a combination of fixed text and one or more variables. The default value is $DOCUMENTBASENAME.
Patterns
The field is a multi-line text field where you enter the patterns to match, one pattern per line. You can use the usual text-editing methods to enter and edit the patterns.
Try
This text field allows you to test the patterns against any arbitrary string you type in.
Preflight Action
Pass when
If you have selected Preflight Action, you have three options:
No actions fail: The documents or pages are sent to the upper flow when the test condition succeeds.
Any action fails: The document or pages are sent to the upper flow when at least one of the selected actions fails the condition.
All actions fail: The document or pages are sent to the upper flow only when all the selected actions fail the condition.
Actions
Select the actions you want to test.
Preflight Profiles
Pass when
If you have selected a Preflight Profile from the drop-down list, you have four options:
has no errors
has no errors or warnings
has errors
has errors or warnings
doc. version 13.1.1