This section describes the relationship between the design document classification tree and the Enum typing hierarchy. A very similar model is used for the Template documents.
Details of the properties and functionality exposed by these interfaces are given in the sections that follow.
Without SmartPlant integration
The class tree would not have any relationships to the Enum hierarchy, that is, no SPFObjClassEnumEnum or SPFEnumEnumObjClass relationships. When the document is created, the document is simply related to the relevant classification tree node by the SPFPrimaryClassification, and the SPFClassifiedLevel# relationships are created to the higher nodes.
To support SmartPlant integration
SPFObjClassEnumEnum or SPFEnumEnumObjClass relationships have to be in place to map the classification tree to the Enum hierarchy. The document master realizes the ISPFDocument interface that contains the typing properties used by SmartPlant integration. The SPFDocumentClass realizes the ISPFObjClass that is related the SmartPlant integration Enum hierarchy. When a document is created, it is related to the tree exactly as for the non-SmartPlant integration situation. Additionally, if there are Enums related to the classification tree node, they are used to populate the document typing properties.