Circular dependencies
Can there be circular dependencies among rules in Windchill or Creo.
Example: If rule R0: if A>5 THEN B=4 and rule R1: if B<5 THEN A=4 is an example of circular dependency. It implies that it can be hard to evaluate the order in which rules should be executed and, also, that we may have oscillating values and rule execution that never ends.
The rules in Windchill are not SQL Procedures, but stored in SQL tables and exportable to various formats, for example, XML. For example:

To define your own rules, you apparently have to write such beasts yourself and then load them using.
An example of the subpart to constrain an attribute is:

Where com.ptc.Waiver must be in the range 10..100.
We are trying to get a grip on how circular dependencies are, or are not, allowed nd managed when working with rules and constraints in WC and Creo.

