Available in uniFLOW System:
RPS for Windows
Available in Workflow Roles:
A list of rules based on which a print job should be routed. (described below)
This workflow element introduces conditional workflow execution, based on the value of job properties. It should be used together with the Route to Printer workflow element in order to supersede the Rule Based Routing element, which is deprecated with uniFLOW V5.
Rather than routing a print job to a printer or a workflow directly, this element will introduce a new child connection for every new rule created. The target workflow can then simply be connected to that connection.
Rules may be entered using the graphical editor, or using the advanced mode in the following notation:
(expression1) -> Connection
(expression1) and (expression2) -> Connection
-> Default Connection
Each rule must be in one line.
Note that the expressions are evaluated one by one, starting from the top, and a job which matches one of the expressions, will be sent on to the connection specified.
Each expression is formed in the following way:
<Job Value> <operator> <Argument>
Connection Name: The connection name may be an arbitrary string. On the last line of the rule, the expression may be ommitted, in which case the default connection is executed, e. g. if no expression applies.
Job Values: Here, any value from a job ticket (prefixed with JT_) can be given Alternatively, any result from the uniFLOW Job Scanners (prefixed with JP_) can be evaluated.
Finally, there are a number of predefined values which can be evaluated, such as: JX_Cardinality (the total page count of the job (JP_Copies * JP_PageCount) JX_AmountPaid (the total price of the job). Naturally, any scan properties defined by the 'SP_' prefix are available as well.
Operator: Can be one of =,<>,<=,<,>,>=,'Contains', 'Except' and '^'
Argument: Can be any argument, such as a number or a string.
By using parenthesis and combinations of and / or, complex expressions and rules can be built.
The following are some examples of valid expressions, together with an explanation:
JX_Cardinality > 400 -> Large Jobs
JX_Cardinality > 50 -> Small Jobs
-> Remaining Jobs
This rule set would execute the connection Large Jobs for jobs with more than 400 pages. Jobs with more than 50 pages would execute via Small Jobs. All other jobs will execute using the Remaining Jobs connection.
(JP_JobName Contains Microsoft Word) and (JX_Cardinality > 50) -> Big Word Docs
-> Other Jobs
This rule set would execute via the Big Word Docs connection all jobs, which have Microsoft Word somewhere in their jobname, AND which have at least 50 pages (page count times copies). All other jobs would be execute via the Other Jobs connection.
(JT_Priority = Urgent) or (JP_UserName = BigChief) -> Important Jobs
(JX_Cardinality > 200) -> Big Jobs
(JP_$Feature:Duplex > 0) or (JP_$Feature:Staple > 0) -> Jobs with Staples
-> Other Jobs
This rule set would execute all jobs which have the job ticket field Priority set to Urgent, or which are printed from the user BigChief via the Important Jobs connection. For jobs that don't match this criteria, but have more than 200 Pages, they're executed via the Big Jobs connection. Finally, jobs that again don't fit this criteria, but which have duplex or stapling commands in them, are executed via the Jobs with Staples connection.
All other jobs would be execute via the Other Jobs connection