How UDAs Appear in the User Interface

Assuming that you make your UDA “Displayed” in both the Search Window and the Cost Guide & Cost Model Info window (but do not make any other changes in Dialog Views), here are some of the default locations where your new UDA will appear. In this example, the new attribute is a basic (non-Dependent) Defined List named “Cost Status” that is both Searchable and Required. It appears (from left to right) on the Search, Cost Guide, and Cost Object Info windows.

UDA Recommended Practice

When you define a UDA that only makes sense for certain Process Groups, use Dependency Contexts (see below) so that your users can edit the UDA only when a relevant Process Group is selected. This approach isn’t always possible, for example for some site variables that require fine control. But it is useful for values such as Booleans like useShortestStockDimensionForPrimarySetup in Stock Machining.