Dependency Context Details
The example in the previous section was very simple to get you started with Dependent UDAs. This section provides more details for more advanced use.
In addition to other UDAs, Dependency Contexts can be defined with Process Group, VPE, and Material selections.
There are a few important things to note about the logic within dependency definitions:
• The order of the Dependency Contexts is important, because the first context that is met will be used (1 through 4 in the screenshot below). It is recommended to have the most specific and highest priority Dependency Contexts at the top of the list.
• Within a given Dependency Context, the logic is evaluated as “or” within a field and “and” from field to field. The context below would read as “if Process Group = [ Casting – Die or Sheet Metal or Casting – Sand ] and VPE = aPriori USA”
• If no values are made available for a given Dependency Context then the UDA will be rendered as read only in the user interface. Users will be able to access a dialog that explains why the UDA is disabled
• You should always define a “terminator context” – a general Dependency Context such as VPE = Any, which will evaluate to true whenever none of the Dependency Contexts above are met.
• If no Dependency Context is met, then all UDA level settings will be used – Required behavior, Default Value, and full Predefined List.
• You MUST ensure that UDAs are implemented in a logical order when configuring the Cost Guide view. Logical order is not enforced by aPriori.