Rule Based Variable Definition

The concept of a rule based variable is to build a variable that will change based on the state of another setting.

For example: If job type is "Digital", THEN change "Image Resolution" check to 150 ppi. AND, IF job type is "Offset" then change "Image Resolution" to 300 ppi.

Rule based variables have two parts, one of the variable used to trigger the Rule, and the other is the variable with the conditions defined. As defined in the example above, the two triggers are "Digital" or "Offset" and the conditional variables are "150" and "300".

To make the Rule Based Variable work you will need to create two variables. One will be a "Constant" variable and the other will be the actual "Rule Based" variable. The Constant variable will be used in the preflight check you want to trigger with the rule based variable.

When both variables are completed they will be assigned to different preflight checks. Both will show up as variable options when the Preflight profile is run only the rule based variable will change automatically if the "trigger" variable is changed.

Following are some screen shots with explanations of how a rule based variable is defined and applied to a Preflight Profile.  This example is based on the following example:

If job type is "Digital", THEN change "Image Resolution" check to 150 ppi.  AND, IF job type is "Offset" then change "Image Resolution" to 300 ppi.

  1. Defining the Constant Value

    The constant value defined here sets the default value to "Offset"
  2. Define the Rule Based variable

    In the Variable value, the constant variable is selected to start the rule statement. In this example, the rule is expanded to two variables "Offset" and "Digital" with each having their own values. If the constant variable which you select here had predefined values set for it (using Interactive Smart Preflight functionality) then those values will be readily available to you here in a dropdown menu.
  3. Assign the rule based variable to a preflight check

    For this check, the Rule based value has been assigned to the Color Ink coverage value. Depending on the previous setting, this value will be set automatically, however the value can still be manually overridden if required when the Preflight Profile is run.
  4. Running the Rule based variable

    When the Preflight Profile is run, the user is presented with the option to modify the variable parameters. In the case of our Rule based variable (TIC Based on Output), entering the right value in the "Output type" will automatically trigger the correct value for the Total Ink Coverage.
  5. AND/OR/ELSE Statements When working with Rule based variables, you can expand the variable argument by adding conditions to a single statement, and/or have multiple statements to reflect different results. Note that each new condition can use the same variable trigger or a different variable trigger.

    AND and OR statements will add a condition to the selected statement. Making so the statement is dependent on two or more conditions.

    ELSE adds an alternative statement to the overall variable, and there is always an exception ELSE statement at the end of the argument so that any exceptions are handled with a preflight error or with a default value.