Siebel Product Administration Guide > Configuration Constraint Template Reference > Procedural Condition Templates >

Procedural-Condition Check Template

The Procedural-Condition Check template has the form:

If procedural condition [item or condition] is true, enforce resultant condition item or condition

You use the Procedural-Condition Check template to check for a precondition. If the item or condition it checks for is true, then the resultant condition is enforced in the solution.

If condition 1 is satisfied before the user clicks, condition2 must be satisfied after the user clicks. Otherwise, an undo only conflict error message is generated. During LoadInstance, this rule is not enforced, because no precondition is satisfied.

For example, consider the following scenario:

Root Product

|_Relationship 1

|_Product A

|_Product B

|_Product C

Constraint: If the procedural condition saying that the quantity of Product A from Relationship 1 equals 1 is true, then enforce the resultant condition saying that the quantity of Product B from Relationship1 equals 1.

Expected Behavior: When Product A is selected and has a quantity of 1, user must select Product B and enter the quantity of 1 before performing any other operation. If the user makes a selection other than Product B, a conflict message is displayed.

The procedural condition applies only to relationships and attributes that are referenced by constraints. For example, consider the following scenario:

Root Product

|_Relationship 1

|_Product A

|_Product B

|_Product C

|_Relationship 2

|_ Product D

|_ Product E

Constraint: If procedural condition the quantity of Product A from Relationship 1 = 1 is true, enforce resultant condition the quantity of Product B from Relationship 1 = 1.

When the user selects Product A and then selects Product C, a conflict message is displayed, because Relationship 1 is referenced within the constraint and relationship items are loaded by the constraint engine. When the user selects Product A and then selects Product D, a conflict message is not displayed, because Relationship 2 is not referenced by any constraint.