Previous | Next | Contents | Index | Navigation | Glossary | Library |
Constraints are of the general syntax:
Function(Object,Attribute) Operator Function(Object,Attribute)
You can define the precedence of evaluation using up to five levels of open and closed parentheses around constraint clauses.
COUNT | Counts the number of times the attribute occurs within the configuration. |
MIN | Returns the minimum value for items with the attribute. |
MAX | Returns the maximum value for items with the attribute. |
QTYSUM | Sums the quantity per parent model of items with the attribute. |
SUM | Sums the total order quantity of items with the attribute. |
VALUE | Returns a specific value for the item with the attribute. |
ATTRIBUTE VALUE LIST | Returns a list of values for a single selected object attribute. |
LITERAL LIST | Returns the list of alphanumeric values specified. |
CHARACTER | Returns the specified character string. |
NUMBER | Returns the specified number. |
USER VALIDATION | Returns the user validation. See: PL/SQL Script 1 or PL/SQL Script 2 |
Note: If the object and attribute referenced in the function does not exist on the order, the Configurator evaluates the functions MIN, MAX, VALUE, and LIST based on the Null Attribute Action. The functions COUNT, SUM, and QTYSUM evaluate to 0.
You can define an unlimited number of configuration attributes. See: Overview of Configuration Attributes
You define attribute values for each object attribute. Then, when you configure products, attributes and their values are evaluated by your product constraints.
You can optionally create regions to group configuration attributes to ease maintenance of attribute values.
> | Greater than. |
< | Less than. |
>= | Greater than or equal to. |
<= | Less than or equal to. |
= | Equal to. |
!= | Not equal to. |
IN | Evaluates whether a specified value exists in the specified list. |
NOT IN | Evaluates whether a specified value does not exist in the specified list. |
NA | No comparison made. Used for autoselection and autoexclusion constraints that use a number of constraint values in the optimization expression, but do not need comparisons. Clauses built with the NA operator do not require a right side. |
Example 1
Assume you need a constraint to ensure that the memory ordered for a laptop PC is sufficient for the most demanding software ordered. Also, add a constraint to recommend additional memory to increase performance. A valid constraint clause for these two rules may look like the following:
((amount of memory ordered) = (amount of memory required)
AND
(recommended memory) > (amount of memory required))
Function | Object/Attribute Type | Return Value Type |
---|---|---|
COUNT | All item attributes except List and Item Name | Number |
SUM | Numeric attributes of items | Number |
QTYSUM | Numeric attributes of items | Number |
MIN | All item attributes except List and Item Name | Number or Character |
MAX | All item attributes except List and Item Name | Number or Character |
VALUE | All object/attributes except List | Number or Character |
USER VALIDATIONS | All object/attributes except List | Number or Character |
LIST | Attribute value lists and literal lists | Set of values |
NUMBER | Literal numbers | Number |
CHARACTER | Literal characters | Character |
Table 3 - 3. |
Previous | Next | Contents | Index | Navigation | Glossary | Library |