Object node - Intergraph Smart Construction - 2019 (7.0) - Configuration - Hexagon PPM

Intergraph Smart Construction API and Programming Reference (2019)

PPMProduct
Intergraph Smart Construction
PPMCategory_custom
Administration & Configuration
SPCVersion_custom
2019(7.0)

An object node represents an instance of a data item to be transferred. For example, you may want to transfer a Materials Forecast Request from Smart Construction to a materials management system. That request would exist inside the container as an object node. An object node can take on many different appearances. The following properties are required for every object and must be present:

  • UID – the globally unique identifier (UID) for the object

  • Name – the name of the object

  • Description – the description of the object

An example of an object node follows:

<SC_ForecastRequest>

<IObject UID="1813e05d-3d65-4d46-8548-d9072514e408" Name="FR-001" Description="Forecast Request 001" />

<IDocumentItem />

<INonDrawingItem />

<ISC_DrawingNumberCollection />

<ISC_FR_WarehouseCollection />

<ISC_ForecastRequest SC_RorecastRequest_ProjectID="Proj-1234" />

<IWBSItem WBSItemPurpose="@{7BE1E73C-F9DD-4FA3-BABB-2D07B817039E}" />

</SC_ForecastRequest>

  • The ClassDef of the object type names the root node. In the example above, the object is an SC_ForecastRequest. The root node of the object is SC_ForecastRequest.

  • The child nodes of the object node are the interfaces realized by the ClassDef of the object. Every ClassDef must realize the IObject interface.

  • The other child nodes of the object node are different interfaces realized by the ClassDef of the object node.

  • All of the realized interfaces that are required must be present inside the object node.

See Also

Data format primer