Once the classification tree has been modeled, you must set the ClassDefs that will be managed by this tree. The tree can manage multiple families, for example, an Asset Model and variant. Each family can use different ClassDefs to represent objects from different nodes of the tree, which is why a specialized Relationship Definition has to be configured.
The classification tree objects are created with different optional interfaces to control the availability of the methods and relationships:
-
ICSTAssetClassification
-
ICSTModelClassification
-
ICSTVariantClassification
The core functionality provides the relationships between the classification tree and the classified objects. However, it may be necessary to configure separate shortcut menu expansion options to each class. To do this, configure an EdgeDef:
-
Starting Interface: ICSTAssetClassification
-
Path: SPFPrimaryClassification
-
End Interface: ICSTAsset (to only show assets)
Similarly for the Model and Variant.
This cannot be done in the Schema Editor; therefore, copy and paste from a core schema
(search for SPFObjClassClassDef in the files).
Then relate the relevant Asset ClassDefs to the different nodes of the classification tree. See the delivered Equipment Class tree as an example.
Now that the classification tree has been linked to the ClassDefs that it manages, create the Relationship Definitions to instantiate objects, that is, the Relationship Definition that will link the equipment to the tree.
Even if the tree is managing more than one family, a single Relationship Definition could be configured if there is a common interface on all the ClassDefs in the different families. For example, a Relationship Definition between ImyEquipClass and ImyEquipment. (This Relationship Definition will be a specialization of SPFPrimaryClassification.) This would give just one shortcut menu expansion, such as 37, on the class tree.
For individual relationship expansions, create separate Relationship Definitions between ImyAssetClass and ImyAssetEquipment.
If a second classification tree (for example, Vendors) is to be configured to classify the same objects, then this second tree has to be related with a Relationship Definition, that is, a specialization of SPFItemClassification because only one tree can be related by SPFPrimaryClassification.