Object Class Manager

Allows managing Object Classes and their Class Fields.

Please remember that you cannot edit Object Class settings for the currently activated System Configuration.

Please refer to the header of the Object Class Manager to identify which Configuration you are trying to change.

HyperDoc classes support inheritance, which enables the grouping of entities such as all Ground Object classes, Building Types, or Equipment.

This feature is not only for organizational purposes but also facilitates understanding within HyperDoc Perspectives. For further information, refer to Perspective sets.

Adding new Object Class

Content Allowed - if checked, objects of this class can have drawings or files attached to them.

Class Fields

Required
Label Field
ID FIeld
Dynamic
Inherited

Field Types

Changing the type of a field is not supported. This capability will be blocked from version 4.4.0 onwards, as it often leads to data loss and database errors. It is recommended to add a new type of field instead. Subsequently, the data can be exported and imported into the database manually using ObjectData import, for example.

Field Sequence

To set a specific sequence, you can either utilize the Drag & Drop functionality or use the sort function available for each header.

Once you have achieved a satisfactory sequence, simply select 'Save'.

Objects With Content

Object class structure should not be confused with the object structure as used in Tesslets, for example, a tree structure.

The building structure is obtained via Perspective sets.

Good Example:	Bad Example:

Good Example:	Bad Example:

Important

In HDC, documents are also viewed as objects. When choosing the "Content allowed" option, we are signifying that attachments or Tessel Composite Documents can be linked.

Change Object Class (Convert)

This functionality enables the transformation of an object from one class to another. For example, a user can convert one (or more) objects of type "Architect" to a "Mark" object.

"Conversion" processes entail two primary actions:

The deletion of the selected object, which requires delete rights to the source object.
The creation of a new object of the chosen type, preserving all metadata from the source object if the fields of both classes correspond. This operation necessitates edit rights to the target class.

How to steps:

On the Grid, select all the objects you want to convert to a different object type (class).
Click on the Add to Object Set button.
On the Object Set window check desired objects again and click on Convert button
From Class Picker window choose your target class and click Select button

Although conversion can be made to any class, its recommended to use “sibling” class. (For example, between sub-classes of Document class)

This will ensure that most metadata is migrated to a new class.

Click Yes on confirmation window and inspect Object Conversion Status window

Conversion will fail if target class has a required field that is not present in the source class.

Conversion of Class and Versioning / Drafts

Class conversion is not versioned. It represents a system-wide, cross-version change.

The resulting changes will be visible in all versions, whether they are made in a draft or the Master Archive!