Data Model Management
There are two ways to implement the data model.
Without Customizing Data Model
All the raceway parts are created from the four classes delivered by default. For each class, you must define the list of your part subtypes associated with this class. You can use this mode if you do not need to add dedicated attributes on each part subtype.
Part Subtype | Behavior Class |
---|---|
Cross | Raceway_Cross |
Tee | Raceway_Tee |
Reducing Tee | Raceway_Tee |
Elbow | Raceway_Elbow |
Reducer | Raceway_Reducer |
etc. | etc. |
Customizing Data Model
With this implementation, the number of part subtypes and classes is the same. Create one class for each part subtype. For each class, you can create the dedicated attributes you want for this class.
Part Subtype | Behavior Class |
---|---|
Cross | DS_Cross (derivate from Raceway_Cross) |
Tee | DS_Tee (derivate from Raceway_Tee) |
Reducing Tee | DS_Reducing_Tee (derivate from Raceway_Reducing_Tee) |
Elbow | DS_Elbow (derivate from Raceway_Elbow) |
Reducer | DS_Reducer (derivate from Raceway_Reducer) |
etc. | etc. |
DS_xxx is the new class created with the customization data model. For more information, see Unified Typing Configuration Tools.