A condition matches document type attributes against decision points and routes the documents to different paths based on the specified attribute and value combinations.
The document type attributes against which conditions can be created are predefined in Sterling Selling and Fulfillment Foundation. You can use these attributes in any combination or you can create conditions that run the appropriate application logic for specific circumstances.
For example, at a certain point in a Sales Order Fulfillment process-type pipeline, you set up a condition to determine if an order contains hazardous materials. When an order reaches this condition in the pipeline, it cannot move any further until the condition is met with a definitive ‘yes' or ‘no' value. In this example, if the order contains no hazardous materials, the value is ‘no' and the order continues through the regular pipeline. If the order does contain hazardous material, the value is ‘yes' and the order is sent down an alternate branch of the order pipeline that has been configured to deal with hazardous material orders.
The behavior of a static condition differs between different flows (for example, SDF, Pipeline, Pipeline Determination Rule, and Event Handlers) based on the data that is available for condition evaluation.
Dynamic conditions provide complete visibility into the incoming flow data and flexibility for evaluating any kind of simple or complex conditions.