Due to the increasing usage and popularity of Knowledge Fusion, we have started increasing the KF class coverage over the NX core functionality. We automatically generate Knowledge Fusion classes (As well as NX Open APIs) through a tool called common API. These automatically generated classes start with the prefix “nx_”. The conventional KF class started with the prefix “ug_”.

Note that there may be a corresponding nx_ class for a given ug_ class. The end results of such corresponding classes may be the same though there are some key differences as follows:

• nx_ classes are auto-generated while ug_ classes were manually written

• nx_ classes support the concept of sub-objects (for example, nx_revolve needs sub-objects nx_axis and ug_section) while ug_ classes intake corresponding attributes.

• nx_ classes have strict default handling as compared to ug_ classes. For example, the nx_null() identifier needs to be passed if no value of the attribute is provided.

• Class attribute lists can be longer because of name-value pair lists. For example, RPO_Dimensions attribute of nx_hole is a long list.

• Some attributes of nx_ classes may have different names from ug_ classes. For example, suppress? in ug_ classes is suppressed in nx_ classes

• Error handling in nx_ classes is as per NX standards.

• The inheritance structure of nx_ classes is different from ug_ classes. For example nx_arc inherits from nx_arc_modifier, nx_arc_host and %nx_arc.

• Knowledge Fusion Navigator→ Add Child Rule

• nx dfa libraries