Using the condition builder
You can use the condition builder to create condition values. To use the condition builder you must first select the field(s) to be analyzed when the condition is used and associate the proper value with them.
For example, you want to set up a condition to search for a specific node for order fulfillment, in this example SN1. To set up this condition value, select Ship Node from the list of available order fulfillment fields. From the drop down list select ‘Is' and enter SN1 as the value and choose Add. You have now created a condition value that reads "Ship Node is ‘SN1'". This indicates that when this condition is used the application checks the document to see if it is associated with SN1, if it is the document moves through the pipeline as per your configuration.
You can also check for conditions to be evaluated if they are greater than, greater than equal to, less than, less than equal to and contains based on the fields you have selected.
You can build more complex strings when creating a condition value using the condition builder. For example, you decide that along with setting up a condition value associated with SN1, you do not want the condition to include any item IDs associated with Item1. To set up this condition value, select Ship Node from the list of available order fulfillment fields. From the drop down list select ‘Is' and enter SN1 as the value and choose Add. Then select the statement and choose the open and closed parentheses buttons. After this statement is set up, select Item ID from the list of available order fulfillment rules. From the drop down list select ‘Not Equal To' and enter Item1. Select the statement and choose the & button, then choose the open and closed parentheses buttons. You have now set up a statement to read "(Ship Node Is ‘SN1') AND (Item ID Not Equal To ‘Item1'). This statement indicates that when this condition is used, the application looks at a given document to see if it is associated with SN1 but not Item1. If this is the case the document goes along the pipeline as per your configuration.
You can add custom attributes by process types and during condition definition to be evaluated as part of the condition builder functionalities.