You are here:
Order Decomposition Conditions
Decomposition relationships sometimes have associated conditions. A condition rule places a condition on the decomposition relationship. Order Management initiates decomposition of an order item only if the specified condition evaluates as true. Otherwise, Order Management skips the decomposition relationship.
Condition rules can evaluate attributes or fields on the order item, as well as other fields that are related to the order item as long as the entire order is included in the fulfillment request.
Condition data is case-sensitive, and are supported only on the first level of decomposition, not on subsequent levels.
If the Source Attribute/Field is left blank and there is a value in the Value field, then the condition evaluates to True or False, depending on the operator:
-
If the operator is =, then the condition evaluates to False.
-
If the operator is !=, then the condition evaluates to True.
-
If the operator is contains, then the condition evaluates to False.
-
If the operator is doesnotcontain, then the condition evaluates to True.
-
If the value for an attribute is not set and there is no default value, then the value of that attribute is considered null. Null values are carried to an empty string.
-
If an attribute is missing from a product, the particular mapping rule or condition is considered invalid and ignored. Invalid conditions evaluate to false.
-
Similarly, a field is considered null if it is null in the database. If the field referred to in a mapping rule or condition does not exist, the corresponding condition or mapping rule is considered invalid.
In Order Management Standard, if an attribute on the left-side has a value of 0, the right-side is left blank, and the operator is =, !=, <, >, <=, or >=, then the empty value on the right side will be considered 0 and the condition is considered True.
