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 Order Management System Software. 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.
- In SDF, the entire flow or input data is available for condition evaluation.
- In case of a Pipeline Determination Rule, only a limited set of published data (per process type) is available for condition evaluation.
- In Pipeline or Events, only a limited set of published data (per entity or event) is available for condition evaluation. For more information on Keydata of the concerned event, refer to Javadoc.
- The Enter your own attribute configuration is applicable only for unexposed key
attributes that are predefined by Sterling Order Management System Software as opposed to any XML
attribute that you can enter. Also, this configuration has limited visibility to the contextual
condition and hence it is not reusable. When there is a need for reusability across conditions,
extn_conditionbuilder.xmlshould be used which forces the metadata for condition builder configurations.Note: In a pipeline, a false node of a condition can be linked to another condition whereas a true node cannot be linked to another condition.
Dynamic conditions provide complete visibility into the incoming flow data and flexibility for evaluating any kind of simple or complex conditions.